Re: HTTP/1.1 non-compliance on POST request handling?

From: Henrik Nordstrom <hno@dont-contact.us>
Date: Wed, 14 Jan 2004 09:59:21 +0100 (CET)

On Wed, 14 Jan 2004, David Luyer wrote:

> A customer of ours is complaining that they have an embedded device,
> which is attempting to connect to a server it knows to be HTTP/1.1
> compliant (as the device and server are from the same vendor), and
> our transparent proxy is intercepting the connection and rejecting it
> due to the lack of a content length header.

Yes, this is because your proxy is HTTP/1.0 and this makes the assumption
made by the application designer no longer valid.

Yet another reason why interception proxying is a gross violation of
TCP/IP and should not be taken lightly.

> Comments? The code in question is around line 3070 of client_side.c
> (and the if statement directly above that one is also relevant).

Until chunked transfer encoding is implemented Squid has no choice of
dropping the request.

What you can do is to allow accesses to the required server directly
without interceptign their requests.

Regards
Henrik
Received on Wed Jan 14 2004 - 01:59:28 MST

This archive was generated by hypermail pre-2.1.9 : Sat Jan 31 2004 - 12:00:10 MST