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
