On Wed, Mar 06, 2002 at 04:40:04PM +0200, Graham Leggett wrote: > > Is there any specific behaviour of the v1.3 proxy that violates > HTTP/1.1?
Just noticed today when I tried the Apache-1.3 proxy: % netcat myproxy 80 <<. HEAD http://microsoft.com/favicon.ico HTTP/1.0 . HTTP/1.1 404 Date: Thu, 14 Mar 2002 11:13:50 GMT Server: Apache/1.3.24-dev (Unix) cache-control: no-store, private Content-Length: 20048 Content-Type: text/html Expires: Thu, 14 Mar 2002 11:14:05 GMT P3P: CP='ALL IND DSP COR ADM CONo CUR CUSo IVAo IVDo PSA PSD TAI TELo OUR SAMo CNT COM INT NAV ONL PHY PRE PUR UNI' Pragma: no-cache Via: 1.1 myproxy:80 (Apache/1.3.24-dev) X-Cache: MISS from myproxy Connection: close Uhhh... -- Microsoft uses Apache-1.3.24-dev? That *MUST* be an error! ;-) Looks like the proxy no longer keeps the original Server: line from the origin server's response, but replaces it by its own. That is in violation of RFC2616: 14.38 Server The Server response-header field contains information about the software used by the origin server to handle the request. The field can contain multiple product tokens (section 3.8) and comments identifying the server and any significant subproducts. The product tokens are listed in order of their significance for identifying the application. Server = "Server" ":" 1*( product | comment ) Example: Server: CERN/3.0 libwww/2.17 --> If the response is being forwarded through a proxy, the proxy --> application MUST NOT modify the Server response-header. --> Instead, it SHOULD include a Via field (as described in --> section 14.45). Martin -- <[EMAIL PROTECTED]> | Fujitsu Siemens Fon: +49-89-636-46021, FAX: +49-89-636-47655 | 81730 Munich, Germany
