Just to clarify... Unless a case is clearly demonstrated where HTTP/1.1 protocol is being used with a client that should have been negotiated down to HTTP/1.0, then this is not a defect. We should not change the "HTTP/1.1" string in the response.
Bill > I quickly reviewed the PR and the example does not demonstrate the reported problem. >The > response is HTTP/1.0 compliant. That the server responds with "HTTP/1.1" is not relevant. > > Bill > > ----- Original Message ----- > From: "William A. Rowe, Jr." <[EMAIL PROTECTED]> > To: "Developers" <[EMAIL PROTECTED]> > Sent: Monday, April 22, 2002 12:50 PM > Subject: Bug: Can't force http 1.0 > > > > Anyone care to try reproducing this bug on non-Win32, to reassure us > > that it's a general bug across platforms? > > > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8357 > > > > Thanks. > > >
