It looks like I'm probably going to get fobbed off by this site's administrators. "It's our load balancer" — "Simply set up a bypass" etc.
Is there any straightforward way to disable the X-Forwarded-For header just for requests to this one website? What would be implications of that be? Dan On 5 July 2016 at 15:07, Dan Charlesworth <d...@getbusi.com> wrote: > That’s a super helpful analysis, thanks Amos. > > Now to see if I track down the site admins 🙃 > > > On 5 Jul 2016, at 3:04 PM, Amos Jeffries <squ...@treenet.co.nz> wrote: > > > > On 5/07/2016 4:25 p.m., Dan Charlesworth wrote: > >> This website seems not send back a proper web page if the request comes > via a (squid?) proxy. > >> > >> http://passporttosafety.com.au/ > >> > >> Can anyone tell what might be going wrong here? > >> > > > > Happens whenever it sees an X-Forwarded-For header. > > > > It looks to me like the server or a script in the origin is trying to > > use that header for something (usually tracking the user by IPs) but > > very broken and crashing. A sadly common situation. > > > > In this case though there is a Varnish proxy in front of it adding a > > "Content-Length: 0" header to 'fix' the problem when the response > > payload fails to appear before the origin connection aborts. > > > > Amos > > > > _______________________________________________ > > squid-users mailing list > > squid-users@lists.squid-cache.org > > http://lists.squid-cache.org/listinfo/squid-users > >
_______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
