httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <>
Subject Re: bug with proxy TRACE? (fwd)
Date Fri, 21 Feb 1997 18:49:51 GMT
No we're still 1.1 compliant, we never claimed the proxy was 1.1... and
TRACE isn't part of 1.0.  Not that I disagree that this is a bug.  It's
just that our proxy wouldn't do the right thing with a trace anyhow.  At
least it's not apparent on some quick reading of the code. 

The other thing is that 1.1 says that the server MUST accept absoluteURI
even though clients don't generate it on non-proxied 1.1 requests.
However, we use the presence of an absoluteURI to set r->proxyreq which is
not quite correct when there is a real 1.1 proxy in the server.  For
example, if you go to host foo, and give it http://foo/bar that isn't a
proxied request.


On Fri, 21 Feb 1997, Alexei Kosut wrote:

> On Fri, 21 Feb 1997, Dean Gaudet wrote:
> > Responses from our proxy should be downgraded to 1.0 until it is a 1.1
> > proxy... 
> They are. The problem is that the proxy is not getting the TRACE
> request. It seems to be processed by the server itself - which is
> wrong, if it's a proxy request. Apache should be checking r->proxyreq
> before sending a trace response. If it's set, it should not send the
> trace response itself, but should let the proxy handle it (even if it
> fails, that's actually better than an incorrectly-send response by the
> server, because the client can then gracefully handle it somehow).
> I think originally, when I wrote the trace code, it did this, but Roy
> had it changed (and he recently changed it again, but I don't think that
> changed it), and apparently this got messed up somewhere.
> This should defenitely be fixed, because it makes Apache non-HTTP/1.1
> compliant.
> -- 
> ________________________________________________________________________
> Alexei Kosut <>      The Apache HTTP Server
> URL:

View raw message