Henrik, I came across this email in the archive. I appreciate that squid is not supposed to be HTTP/1.1 compatible but I was wondering if you knew what would be involved in adding support for this message? Would you be able to tell me where I should start looking if I was to try and add support for it myself? Thanks for any help you can give! Graeme -----Original Message----- From: Henrik Nordstrom [mailto:hno@xxxxxxxxxxxxxxx] Sent: 05 August 2005 11:38 To: Jean Ressouche Cc: Squid Users Subject: Re: Squid sqeeze http 100 Continue messages ? On Mon, 1 Aug 2005, Jean Ressouche wrote: > i try to use some application through squid, but some of them bug a little > bit ... > i've catch the tcp packet, and see a difference between direct connect packet > and thruough squid packets ... > the server side reply like "HTTP/1.1 100 Continue" is missing (i think i need > them for my application)... Squid is HTTP/1.0. "HTTP/1.1 100 Continue" requires HTTP/1.1. >From the HTTP/1.1 RFC 2616 regarding this situation: Because of the presence of older implementations, the protocol allows ambiguous situations in which a client may send "Expect: 100- continue" without receiving either a 417 (Expectation Failed) status or a 100 (Continue) status. Therefore, when a client sends this header field to an origin server (possibly via a proxy) from which it has never seen a 100 (Continue) status, the client SHOULD NOT wait for an indefinite period before sending the request body. But it would probably be a good idea to extend Squid to immediately respond with 417 if a request with "Expect: 100-continue" is seen to allow the client to recover in a timely fashion. Please file an enhancement request for this in out bug reporting tool http://www.squid-cache.org/bugs/ and I'll send you a patch (patch already prepared, but squid-users is not the correct forum for patches) Regards Henrik This message has been scanned for viruses by BlackSpider MailControl - www.blackspider.com
