RE: cookie insert method secure

2018-06-25 Thread mlist
ion in reliance on it. If you have received this email in error, please notify the sender and delete this email from your system. From: Igor Cicimov Sent: lunedì 25 giugno 2018 06:12 To: mlist Cc: haproxy@formilux.org Subject: Re: cookie insert method secure On Sun, Jun 24, 2018 at 11:28 PM,

Re: cookie insert method secure

2018-06-24 Thread Igor Cicimov
On Sun, Jun 24, 2018 at 11:28 PM, mlist wrote: > Hi Igor, > > as I see, this is not true. > > > > I think ssl_fs is just persisted between request and response as this work > fine without setting vars (as for below example), *but never works for > cookie header inserted by “cookie insert* …”. It

RE: cookie insert method secure

2018-06-24 Thread mlist
system. From: Igor Cicimov Sent: domenica 24 giugno 2018 10:54 To: mlist Cc: haproxy@formilux.org Subject: Re: cookie insert method secure On Wed, Jun 13, 2018 at 2:23 AM, mlist mailto:ml...@apkappa.it>> wrote: Hi, there is a mechanism to specify to command like: cookie insert indir

Re: cookie insert method secure

2018-06-24 Thread Aleksandar Lazic
you should not copy, modify, distribute or take any action in reliance on it. If you have received this email in error, please notify the sender and delete this email from your system. -Original Message- From: Aleksandar Lazic Sent: martedì 12 giugno 2018 23:29 To: mlist Cc: haproxy@for

Re: cookie insert method secure

2018-06-24 Thread Igor Cicimov
On Wed, Jun 13, 2018 at 2:23 AM, mlist wrote: > Hi, > > there is a mechanism to specify to command like: > > > > cookie insert indirect preserve nocache httponly secure > > > > to insert secure only if the session is ssl ? So it is possible to use > this command on a common http/https backend wi

RE: cookie insert method secure

2018-06-24 Thread mlist
bute or take any action in reliance on it. If >you have received this email in error, please notify the sender and delete >this email from your system. > > > > > >-Original Message- >From: Aleksandar Lazic >Sent: martedì 12 giugno 2018 23:29 >To: mli

Re: cookie insert method secure

2018-06-23 Thread Aleksandar Lazic
ibute or take any action in reliance on it. If you have received this email in error, please notify the sender and delete this email from your system. -Original Message- From: Aleksandar Lazic Sent: martedì 12 giugno 2018 23:29 To: mlist Cc: haproxy@formilux.org Subject: Re: cookie

RE: cookie insert method secure

2018-06-23 Thread mlist
email in error, please notify the sender and delete this email from your system. -Original Message----- From: Aleksandar Lazic Sent: martedì 12 giugno 2018 23:29 To: mlist Cc: haproxy@formilux.org Subject: Re: cookie insert method secure Hi. On 12/06/2018 18:05, mlist wrote: >Hi Alekandar,

Re: cookie insert method secure

2018-06-12 Thread Aleksandar Lazic
mente riservate. This email is confidential, do not use the contents for any purpose whatsoever nor disclose them to anyone else. If you are not the intended recipient, you should not copy, modify, distribute or take any action in reliance on it. If you have received this email in error, please notify

RE: cookie insert method secure

2018-06-12 Thread mlist
you have received this email in error, please notify the sender and delete this email from your system. -Original Message- From: Aleksandar Lazic Sent: marted? 12 giugno 2018 19:29 To: mlist Cc: haproxy@formilux.org Subject: Re: cookie insert method secure Hi. On 12/06/2018 16:23

Re: cookie insert method secure

2018-06-12 Thread Aleksandar Lazic
Hi. On 12/06/2018 16:23, mlist wrote: Hi, there is a mechanism to specify to command like: cookie insert indirect preserve nocache httponly secure to insert secure only if the session is ssl ? So it is possible to use this command on a common http/https backend without using 2 different redu