Re: [squid-users] 502 Bad Gateway
Hi Eliezer I have found the solution. I have change the option forwarded_for from “off” to “delete and now it’s working(option via off was ok). I have resolved also the problem with streaming video ( 06/17/2014 11:55 AM). Thank you Maurizio
Re: [squid-users] 502 Bad Gateway
On 15/07/2014 1:14 a.m., ama...@tin.it wrote: Hello I have a problem with - squid-3.3.9 - squid-3.4.5 but NO problem with: - squid-2.7.stable9 - without proxy I have tested with firefox 24.6 and ie explorer 8.0. On browser the error displayed is: The following error was encountered while trying to retrieve the URL: http://www.regione.lombardia.it/ Read Error The system returned: (104) Connection reset by peer This domain seems to be amongst the set which crash if they happen to encounter any one of many valid X-Forwarded-For header contents. X-Forwarded-For: 127.0.0.1,127.0.0.1 X-Forwarded-For: ::1 X-Forwarded-For: unknown Amos
Re: [squid-users] 502 Bad Gateway
Hey There, We do not have a clue about your setup(you didn't shared any relevant information). What OS are you using? Is it a self compiled version of squid? Is this a reverse or forward proxy? You can use this script: http://www1.ngtech.co.il/squid/basic_data.sh To share relevant information. You can modify the relevant files location if needed inside the script. This script uses more then just what needed in your case but it won't do any harm by sharing this information. Eliezer On 07/14/2014 04:14 PM, ama...@tin.it wrote: Hello I have a problem with - squid-3.3.9 - squid-3.4.5 but NO problem with: - squid-2.7.stable9 - without proxy I have tested with firefox 24.6 and ie explorer 8.0. On browser the error displayed is:
Re: [squid-users] 502 Bad gateway
On Sat, 2012-10-13 at 18:05 +1300, Amos Jeffries wrote: On 13/10/2012 2:18 a.m., Leonardo wrote: Hi, I'm getting 502 bad gateway while attempting to access the site ibs.it. This happens with squid 3.2.2 and 3.2.0.19 at least. It does not happen with squid 2.7.x series (not tested with all minor revisions though). Anyone else getting the same error? Beyond the generic HTTP status code what else do you have? Squid logs and the content of that 503 response would be helpful. 1350283892.429129 10.44.65.254 TCP_MISS_ABORTED/200 2901 GET http://www.ibs.it/ - HIER_DIRECT/www.ibs.it text/html I've dumped the traffic with squid and without squid (it works without proxy), and as far I could tell, there's no reverse proxy doing bad stuff. It's not about a reverse proxy. It's about something somewhere in the relay chain not being available. The error page itself will tell more. 502 Bad Gateway The server returned an invalid or incomplete response. The answer from the site appears to be same in both cases. With squid, I see that after the second response packet, after the GET request, my proxy closes the connection with FIN,ACK, and all subsequent response packets get an RST. Sounds perfectly normal behaviour for TCP shutting down a connection. But are you saing the proxy sends FIN or FIN+ACK ? which one determines which end is doing the closure. Sorry, I was not clear in that. The proxy sends one packet with FIN,ACK flags, effectively shutting down the connection. What could it be the issue? One of the services needed by Squid to provide a response is not working. Upstream HTTP server, DNS server, ICAP server, helper problem, TCP errors, URL scheme unknown, could be any one of those or something else entirely. I guess I need to turn on some debugging in order to find out what's wrong. I'm trying to figure out the right Section Number to turn on. Thanks! - leonardo signature.asc Description: This is a digitally signed message part
Re: [squid-users] 502 Bad gateway
On 13/10/2012 2:18 a.m., Leonardo wrote: Hi, I'm getting 502 bad gateway while attempting to access the site ibs.it. This happens with squid 3.2.2 and 3.2.0.19 at least. It does not happen with squid 2.7.x series (not tested with all minor revisions though). Anyone else getting the same error? Beyond the generic HTTP status code what else do you have? Squid logs and the content of that 503 response would be helpful. I've dumped the traffic with squid and without squid (it works without proxy), and as far I could tell, there's no reverse proxy doing bad stuff. It's not about a reverse proxy. It's about something somewhere in the relay chain not being available. The error page itself will tell more. The answer from the site appears to be same in both cases. With squid, I see that after the second response packet, after the GET request, my proxy closes the connection with FIN,ACK, and all subsequent response packets get an RST. Sounds perfectly normal behaviour for TCP shutting down a connection. But are you saing the proxy sends FIN or FIN+ACK ? which one determines which end is doing the closure. What could it be the issue? One of the services needed by Squid to provide a response is not working. Upstream HTTP server, DNS server, ICAP server, helper problem, TCP errors, URL scheme unknown, could be any one of those or something else entirely. Amos
Re: [squid-users] 502 Bad Gateway ??
On Sun, 15 May 2005, Phibee Network operation Center wrote: when my users want going on www.pagesjaunes.fr, he have a 502 Bad Gateway and when he connect directly without proxy that's work ... Anything in cache.log? What does access.log say? Regards Henrik
