Re: HTTP 2.0 and a Faster, more Mobile-friendly web

In message <op.wh9pqtcwiw9drz@uranium>, "Martin Nilsson" writes:

>Current HTTP pipelining works fine when it works, but there are a lot of  
>servers that doesn't support it. As soon as you start having more than one  
>outstanding request on a connection you'll run into issues ranging from  
>ignoring subsequent requests (forcing a reissue of the queued requests),  
>to closing the connection as soon as a second request is received  
>(truncating the first response), to scrambling the response (i.e. multiple  
>responses written to the same socket at the same time). 

A surprising number of intermediaries expect HTTP/1.1 request to start
at a packet boundary...

Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

Received on Monday, 30 July 2012 16:42:02 UTC