talking proxy to backends

[Audun Ytterdal]

We have sent in a support request to varnish for the same thing a while
back.

Usually varnish is in some sort of sandwitch.

It could be haproxy -> Varnish -> haproxy, or h2o ->Varnish->nginx or
nginx->Varnish->haproxy or stud->varnish

Where people want to do their logic is up to them. It can always be solved
with http-headers x-forwarded-for and/or x-client-ip, as it has earlier.
But there is a reason why haproxy among others have aded this
functionality. Then suddenly you don't need extra modules like
mod_remote_ip for apache or massage http-headers into ips.
client.ip, accesslogs, varnishlog has a more relevant ip without hacks

* haproxy supports it both as a client and towards backends
* nginx support it as  a client. Patchsets for backends exists (
https://github.com/yaoweibin/nginx_tcp_proxy_module/pull/110)
* h2o supprots is a client and I have a issue for it on github  (
https://github.com/h2o/h2o/issues/602)

It's not a very important thing, can be solved by other means. But it would
be nice.

--
Audun
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20160209/b25a3191/attachment-0001.html>