Upgrading from v3 to v5 - XFF and client.identity

[Andrei]

Oh yeah, Guillaume also has a great post on it @
https://info.varnish-software.com/blog/sticky-session-with-cookies :D

On Tue, Mar 28, 2017 at 6:28 AM, Andrei <lagged at gmail.com> wrote:

> Hi Mark,
>
> I suggest going over the following blog post for the changes you're
> looking for. Good luck moving forward :D
>
> https://info.varnish-software.com/blog/proper-sticky-
> session-load-balancing-varnish
>
>
> On Tue, Mar 28, 2017 at 4:52 AM, Mark Hanford <mark at hanfordonline.co.uk>
> wrote:
>
>> Hi folks. I'm in the process of trying to upgrade our current v3 config
>> to v4+ for upgrading to Varnish 5.
>>
>> In my old v3 config, I use the XFF header to change the client.identity
>> if it is present.
>>
>>     # For session-persistence, set a client identity.
>>     # We're using the client's IP for this to ensure server-persistence.
>>     if (req.http.X-Forwarded-For) {
>>         set client.identity = req.http.X-Forwarded-For;
>>     } else {
>>         set client.identity = client.ip;
>>     }
>>
>> It is important that a request from one remote client goes to the same
>> backend every time, when possible. Do I still need to deal with this, or
>> will this be handled transparently in some way?
>>
>> I suspect I'll have more questions as I go along, so I apologise in
>> advance for the spam :)
>>
>> thanks,
>>
>> Mark
>>
>> _______________________________________________
>> varnish-misc mailing list
>> varnish-misc at varnish-cache.org
>> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20170328/0a525f0e/attachment.html>