tis 2006-09-19 klockan 14:45 -0700 skrev Mark Nottingham: > On 2006/09/19, at 1:54 PM, Henrik Nordstrom wrote: > > >> However, if it receives a HTTP/1.1 request, it will fall back to one- > >> request-per-connection. Since pconns are the default in HTTP 1.1, why > >> not use them? > > > > Because we don't know the HTTP/1.1 client knows HTTP/1.0-style > > persistent connections. > > A HTTP/1.0-style persistent connection is a form of a HTTP/1.1 > persistent connection. I.e., sending this response > > --->8--- > HTTP/1.0 200 OK > Content-Length: nnn > Connection: keep-alive Except that HTTP/1.1 doesn't define "Connection: keep-alive", only "Connection: close". The keep-alive of an HTTP/1.1 connection is implicit by the protocol being HTTP/1.1. "Connection: keep-alive" is keep-alive of a HTTP/1.0+ style persistent web server connection. HTTP/1.0+ defines different signaling for web servers and proxies due to Connection not being an HTTP/1.0 header making it likely proxies does not understand Connection: keep-alive.. A client accepting "Connection: keep-alive" as keep-alive of a proxied connection is broken not respecting the Netscape specifications for keep-alive for HTTP/1.0. Regards Henrik
Attachment:
signature.asc
Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signerad meddelandedel
