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

On Wed, 14 Jan 2004, David Luyer wrote:

> And yet it is so useful in so many ways, not only the performance
> improvement;
>
> * fixes broken DNS lookups from dodgy modem accelerators
>
> * fixes incompatible TCP stacks (OSX-KA9Q becomes OSX->Linux,
> Linux->KA9Q, making a working TCP connection in place of a
> failing one)
>
> * fixes problems with use of satellite for internet by re-terminating
> the TCP session in the middle
>
> * provides potential for anonymization
>
> * fixes MTU breakage in many cases (although it can cause MTU
> breakage as well, if client IPs are rewritten by the L4 switch
> or if MTU related ICMP is not redirected along with the TCP
> packets - this can be tricky to get right)

And so does standard proxying, without the risk of the MTU issue.

> I'm attempting to establish the server IPs and will put an exception
> in the Alteon when done, as long as there aren't too many distinct
> server IPs involved -- otherwise I'd have to look at how much effort
> to implement chunked transfer encoding.

The TE patch has chunked transfer encoding, but has bitrotted somewhat..

Regards
Henrik
Received on Wed Jan 14 2004 - 03:43:15 MST