>>Our main concern is that if we can't find a reliable way to route around
>>this problem we will have to turn off HTTP/1.1 support whenever we are
>>going through a proxy. While we will provide a switch to turn on 1.1,
>>obviously, most users will not use it.
Nasty!
This is probably 'closing the stable door after the horse has bolted' (HTTP
1.1 now being a published spec), but it occurs to me that an trail of
proxies between client and origin server, similar to RECEIVED headers in
RFC822 mail messages, might allow the client to determine the reliability
of the HTTP 1.1 path. I posit that each entry in the trail would contain
host name, HTTP version number and server implementation and version
identification (e.g. "WWW.ACME.COM, HTTP/1.1 (MoonSoft HTTPD V3.28)")
This assumes that legacy proxies in the path which don't add this
information can be detected, which I think should be possible.
GK.
---
------------
Graham Klyne
GK@ACM.ORG