What you describe is certainly not a Squid problem but a web application
incorrectly assuming that a single users requests always comes from the same
IP. Cache meshes is perhaps the most obvious example where this assumption
isn't true, as the IP then varies slightly based on request and/or cache mesh
load conditions.
Regards
Henrik Nordstr�m
Squid Hacker
On Tuesday 13 November 2001 19.55, Jean Risk wrote:
> This looks like a problem in squid.
>
> The way I figured it is that some sites require that the post request
> and the get request are issued from the same IP.
> What happens is that the get request is issued from the parent squid IP.
> But squid treats the post requests differently, as they should not be
> cached, so, the post (by default) is not forwarded to the parent squid.
> As a result, the post request and the get requests are issued from
> different IPs.
>
> It was fixed by forcing all the requests to pass through the parent
> squid by using "never_direct allow all", which is a very bad solution.
> I wish this could be solved in squid.
Received on Tue Nov 13 2001 - 13:27:55 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:04:10 MST