RE: [squid-users] Proxy chaining

I have had the same problem. It seems to happen (for me) when I am doing an
HTTP POST to a webserver running on a non-standard port.

I am running Squid Version 2.4.STABLE3, which uses as a cache-peer a "Mighty
Stupid" proxy server on port 80, which itself routes through a NAT/firewall
thingy that blocks direct access to non-standard web ports. So I think that
Squid is trying to go direct for these POSTs, and they fail because that is
not allowed in our environment.

my cache_peer line
cache_peer MightyStupid.smc.edu parent 80 0 no-query no-digest

I do not have any always_direct or never_direct lines.

I tried commenting out this line which looked very promising:
#hierarchy_stoplist cgi-bin ?
but to no effect.

Steve Hunt
hunt_steve@smc.edu

> -----Original Message-----
> From: Schelstraete Bart [mailto:bart@schelstraete.org]
> Sent: Friday, March 22, 2002 3:32 AM
> To: squid-users@squid-cache.org
> Subject: [squid-users] Proxy chaining
>
>
>
> Gents,
>
> I'm having some problems with my squid, and I hope you can help me.
> I'm running a Squid server, which binds to another proxy
> server on port
> 8080.
>
> That works, but if the user runs a query or something on a website (if
> they press a 'submit' button or something)... it refuses the
> connection,
> like Squid isn't going through the main proxy server.
>
> Does somewhone knows what the problem can be?
>
> rgrds,
>
> Bart
>
> --
> Schelstraete Bart
> Unix/Netscape Administrator
> bschelst@bru-hub.dhl.com
>
> * 'I'm a little source code short and stout. This is my input this is
> my out!' *
>
>
>
>
>
Received on Fri Mar 22 2002 - 11:29:17 MST