[Varnish] #203: X-Forwarded-For handling

Varnish varnish-bugs at projects.linpro.no
Thu Feb 14 10:37:27 CET 2008

#203: X-Forwarded-For handling
 Reporter:  des          |        Owner:  phk  
     Type:  enhancement  |       Status:  new  
 Priority:  normal       |    Milestone:       
Component:  varnishd     |      Version:  trunk
 Severity:  normal       |   Resolution:       
 Keywords:               |  
Comment (by des):

 You are right - there is no formal definition, it is a de-facto standard
 introduced by Squid and later adopted by Apache's {{{mod_proxy}}}.  Many
 web applications have come to depend on it (e.g. ignore a session cookie
 sent by a different client IP than it was originally issued to)

 We currently add an extra header - I'm not sure the backend will interpret
 that correctly.  It may vary from backend to backend.

 re post mode vs pipe mode, yes; but it is possible that the backend will
 be confused (or produce the wrong results) if subsequent requests don't
 include {{{X-Forwarded-For}}}.  That is not our problem, though; it's for
 the admin to decide, and if necessary add {{{Connection: close}}}.

 Anyway, I am not advocating adding any of this logic to the C code.  On
 the contrary, I think {{{X-Forwarded-For}}} handling should be moved from
 C to VCL, so the admin has full control over it, and we can wash our hands
 of it.

Ticket URL: <http://varnish.projects.linpro.no/ticket/203#comment:3>
Varnish <http://varnish.projects.linpro.no/>
The Varnish HTTP Accelerator

More information about the varnish-bugs mailing list