Re: [squid-users] CONNECT errors with 2.7.STABLE2-2
* Henrik Nordstrom [EMAIL PROTECTED]: 1215083751.310 0 10.47.52.76 TCP_MISS/417 1811 CONNECT drm.viasyshc.com:443 - NONE/- text/html 417 is Expectation Failed, and means the application sent an Expect: header which can not be fulfilled by Squid. Most likely this is Expect: 100-continue as it's the only expectation defined in HTTP/1.1. It beats me why one would send that in a CONNECT request, but not strictly disallowed. As we kind of expected there would be applications out there who do not kow how to deal with Expectation failed and retry their requests without the expectation we added a directive to tell Squid to ignore this. Very RFC-ignorant, but... ignore_expect_100 on I added this. Let's see how it goes. 2.6.x behaved differently in this regard? -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED]
Re: [squid-users] CONNECT errors with 2.7.STABLE2-2
On fre, 2008-07-04 at 09:50 +0200, Ralf Hildebrandt wrote: I added this. Let's see how it goes. 2.6.x behaved differently in this regard? Yes. 2.6 is quite ignorant about HTTP/1.1 requirements like Expect. Regards Henrik signature.asc Description: This is a digitally signed message part
Re: [squid-users] CONNECT errors with 2.7.STABLE2-2
Hi Ralf, On Fri, Jul 04, Ralf Hildebrandt wrote: ignore_expect_100 on I added this. Let's see how it goes. 2.6.x behaved differently in this regard? yes and 3.0 behaves differnt, too. I had the same problem with 2.7 so I switched to 3.0 -- Gruß Dieter -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the From field. pgpGr1AVvGaes.pgp Description: PGP signature
Re: [squid-users] CONNECT errors with 2.7.STABLE2-2
* Henrik Nordstrom [EMAIL PROTECTED]: ignore_expect_100 on Before: 1215157781.184 0 10.47.52.76 TCP_MISS/417 1811 CONNECT drm.viasyshc.com:443 - NONE/- text/html 1215157782.410 0 10.47.52.75 TCP_MISS/417 1811 CONNECT drm.viasyshc.com:443 - NONE/- text/html After: 121516.207 3285017 10.47.52.76 TCP_MISS/200 1197769 CONNECT drm.viasyshc.com:443 - DIRECT/63.167.245.76 - 121516.207 3293788 10.47.52.75 TCP_MISS/200 113728 CONNECT drm.viasyshc.com:443 - DIRECT/63.167.245.76 - I praise Henrik (as usual). -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED]
Re: [squid-users] CONNECT errors with 2.7.STABLE2-2
On fre, 2008-07-04 at 10:38 +0200, Dieter Bloms wrote: Hi Ralf, On Fri, Jul 04, Ralf Hildebrandt wrote: ignore_expect_100 on I added this. Let's see how it goes. 2.6.x behaved differently in this regard? yes and 3.0 behaves differnt, too. 3.0 is as ignorant about HTTP/1.1 transports as 2.6 was. Regards Henrik signature.asc Description: This is a digitally signed message part
Re: [squid-users] CONNECT errors with 2.7.STABLE2-2
* Dieter Bloms [EMAIL PROTECTED]: I added this. Let's see how it goes. 2.6.x behaved differently in this regard? yes and 3.0 behaves differnt, too. I had the same problem with 2.7 so I switched to 3.0 I used 3.0.x but was bitten by the empty pages problem...
Re: [squid-users] CONNECT errors with 2.7.STABLE2-2
I wonder why this ignore 100 expect behaviour isn't default.. Henrik, why isn't it default in 2.7 there are issues with the expect handling? Adrian 2008/7/4 Ralf Hildebrandt [EMAIL PROTECTED]: * Dieter Bloms [EMAIL PROTECTED]: I added this. Let's see how it goes. 2.6.x behaved differently in this regard? yes and 3.0 behaves differnt, too. I had the same problem with 2.7 so I switched to 3.0 I used 3.0.x but was bitten by the empty pages problem...
Re: [squid-users] CONNECT errors with 2.7.STABLE2-2
* Adrian Chadd [EMAIL PROTECTED]: I wonder why this ignore 100 expect behaviour isn't default.. Henrik, why isn't it default in 2.7 there are issues with the expect handling? Good question! I would have expected 2.7.x to behave like 2.6.x (well, at least since my switch to 3.0.x didn't break things, I wouldn't expect the change back to 2.7.x to break things). -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED]
Re: [squid-users] CONNECT errors with 2.7.STABLE2-2
On fre, 2008-07-04 at 19:38 +0800, Adrian Chadd wrote: I wonder why this ignore 100 expect behaviour isn't default.. Henrik, why isn't it default in 2.7 there are issues with the expect handling? Processing Expect is a MUST level requirement. The reason this in case of 100-continue this is that the clients can then immediately drop the POST delay timer, avoiding waiting for an 100 Continue which never comes. Regards Henrik signature.asc Description: This is a digitally signed message part
[squid-users] CONNECT errors with 2.7.STABLE2-2
A tool supposedly worked until May and now, due to the evil squid update to 2.7.x, won't work anymore. Of course squid is to blame, as always. Since we all know, the professional tool is written with great care, adhering to the specs and RFC by knowledgeable people. Unlike squid. Of course. Call me bitter. From our logs: 1215083751.310 0 10.47.52.76 TCP_MISS/417 1811 CONNECT drm.viasyshc.com:443 - NONE/- text/html 1215083785.295 0 10.47.52.76 TCP_MISS/417 1811 CONNECT drm.viasyshc.com:443 - NONE/- text/html 1215083805.308 2 10.47.52.76 TCP_MISS/417 1811 CONNECT drm.viasyshc.com:443 - NONE/- text/html 1215083818.308 0 10.47.52.76 TCP_MISS/417 1811 CONNECT drm.viasyshc.com:443 - NONE/- text/html 1215083819.294 0 10.47.52.76 TCP_MISS/417 1811 CONNECT drm.viasyshc.com:443 - NONE/- text/html Their app logs: 07/03/08[11:02:09] ERROR: HTTP Transport: POST HTTP error 417 bytes = 16. Retrying Seq No 4, RetryCount 1(max 1) 07/03/08[11:02:09] DEBUG: HEADER INFO START Server: squid/2.7.STABLE2 Date: Thu, 03 Jul 2008 09:02:10 GMT Content-Type: text/html Content-Length: 1416 Expires: Thu, 03 Jul 2008 09:02:10 GMT X-Squid-Error: ERR_INVALID_REQ 0 X-Cache: MISS from proxy-cbf-2.charite.de X-Cache-Lookup: NONE from proxy-cbf-2.charite.de:8080 Via: 1.0 proxy-cbf-2.charite.de:8080 (squid/2.7.STABLE2) Connection: close HEADER INFO END== How can I debug their crap^h^h^h^hprofessional error free software? -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED]
Re: [squid-users] CONNECT errors with 2.7.STABLE2-2
Attaching the actual request thats being made would probably be a good place to start :) Adrian 2008/7/3 Ralf Hildebrandt [EMAIL PROTECTED]: A tool supposedly worked until May and now, due to the evil squid update to 2.7.x, won't work anymore. Of course squid is to blame, as always. Since we all know, the professional tool is written with great care, adhering to the specs and RFC by knowledgeable people. Unlike squid. Of course. Call me bitter. From our logs: 1215083751.310 0 10.47.52.76 TCP_MISS/417 1811 CONNECT drm.viasyshc.com:443 - NONE/- text/html 1215083785.295 0 10.47.52.76 TCP_MISS/417 1811 CONNECT drm.viasyshc.com:443 - NONE/- text/html 1215083805.308 2 10.47.52.76 TCP_MISS/417 1811 CONNECT drm.viasyshc.com:443 - NONE/- text/html 1215083818.308 0 10.47.52.76 TCP_MISS/417 1811 CONNECT drm.viasyshc.com:443 - NONE/- text/html 1215083819.294 0 10.47.52.76 TCP_MISS/417 1811 CONNECT drm.viasyshc.com:443 - NONE/- text/html Their app logs: 07/03/08[11:02:09] ERROR: HTTP Transport: POST HTTP error 417 bytes = 16. Retrying Seq No 4, RetryCount 1(max 1) 07/03/08[11:02:09] DEBUG: HEADER INFO START Server: squid/2.7.STABLE2 Date: Thu, 03 Jul 2008 09:02:10 GMT Content-Type: text/html Content-Length: 1416 Expires: Thu, 03 Jul 2008 09:02:10 GMT X-Squid-Error: ERR_INVALID_REQ 0 X-Cache: MISS from proxy-cbf-2.charite.de X-Cache-Lookup: NONE from proxy-cbf-2.charite.de:8080 Via: 1.0 proxy-cbf-2.charite.de:8080 (squid/2.7.STABLE2) Connection: close HEADER INFO END== How can I debug their crap^h^h^h^hprofessional error free software? -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED]
Re: [squid-users] CONNECT errors with 2.7.STABLE2-2
* Adrian Chadd [EMAIL PROTECTED]: Attaching the actual request thats being made would probably be a good place to start :) Yes, how do I log this? -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED]
Re: [squid-users] CONNECT errors with 2.7.STABLE2-2
On tor, 2008-07-03 at 16:43 +0200, Ralf Hildebrandt wrote: A tool supposedly worked until May and now, due to the evil squid update to 2.7.x, won't work anymore. Of course squid is to blame, as always. Since we all know, the professional tool is written with great care, adhering to the specs and RFC by knowledgeable people. Unlike squid. Of course. Call me bitter. From our logs: 1215083751.310 0 10.47.52.76 TCP_MISS/417 1811 CONNECT drm.viasyshc.com:443 - NONE/- text/html 417 is Expectation Failed, and means the application sent an Expect: header which can not be fulfilled by Squid. Most likely this is Expect: 100-continue as it's the only expectation defined in HTTP/1.1. It beats me why one would send that in a CONNECT request, but not strictly disallowed. As we kind of expected there would be applications out there who do not kow how to deal with Expectation failed and retry their requests without the expectation we added a directive to tell Squid to ignore this. Very RFC-ignorant, but... ignore_expect_100 on Regards Henrik signature.asc Description: This is a digitally signed message part
Re: [squid-users] CONNECT errors with 2.7.STABLE2-2
On tor, 2008-07-03 at 20:16 +0200, Ralf Hildebrandt wrote: * Adrian Chadd [EMAIL PROTECTED]: Attaching the actual request thats being made would probably be a good place to start :) Yes, how do I log this? log_mime_hdrs on Regards Henrik signature.asc Description: This is a digitally signed message part
