mån 2008-01-14 klockan 10:29 +0900 skrev Adrian Chadd: > No, Squid-2.7 doesn't support all of HTTP/1.1. Squid-2 is just starting to grow > the internal restructuring that will make HTTP/1.1 compliance easier to achieve > without massive shoehorning and sledgehammering of the required concepts. > It at least decodes chunked encoded responses from HTTP servers which shouldn't > be responding with it to a HTTP/1.0 request. It actually does a fair bit more than that, but no it's not yet full HTTP/1.1. The major things missing at the moment is processing of 1xx responses and handling of Expect headers. It's enought of HTTP/1.1 to allow Squid to advertise itself as HTTP/1.1 in day-to-day usage for browsing, primarily for reverse proxies. Enabling this for Internet proxying until there is support for 1xx and Expect is a little scarier, but probably works better than 2.6 for most.. Regards Henrik
Attachment:
signature.asc
Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signerad meddelandedel
