You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by "William A. Rowe, Jr." <wr...@rowe-clan.net> on 2002/04/22 18:50:49 UTC
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.
Re: Can't force http 1.0
Posted by "Roy T. Fielding" <fi...@apache.org>.
On Monday, April 22, 2002, at 11:11 AM, Joshua Slive wrote:
> Bill Stoddard wrote:
>
>>> SetEnv force-response-1.0
>>>
>>> According to the docs here:
>>> http://httpd.apache.org/docs/env.html#special
>>> The point of that was to deal with silly proxies that belched when they
>>> saw "HTTP/1.1" (regardless of the actual protocol version of the
>>> response).
>
>> Really? I don't intuit that from the doc though you may be right. The
>> behaviour being
>> observed is how 1.3 has been working for years (pretty sure anyway) and
>> to the best of my
>> knowledge, it is not breaking anything. Would be interested in knowing
>> what exactly is
>> breaking with this PR.
>
> I guess I'm reading that in the context of
> http://httpd.apache.org/info/aol-http.html
> and I'm also asking the question "What does force-response-1.0 do that
> downgrade-1.0 doesn't do?"
downgrade-1.0 is for ignoring client requests that indicate HTTP/1.1 but
we know the client is broken and cannot deal with HTTP/1.1 features.
We send an HTTP/1.1 response using only 1.0 features.
force-response-1.0 is for dealing with clients that simply cannot parse
the HTTP/1.1 version number. For these we send an HTTP/1.0 response
using only 1.0 features.
They are both needed, though I wouldn't consider it a high priority.
....Roy
Re: Can't force http 1.0
Posted by Joshua Slive <jo...@slive.ca>.
Bill Stoddard wrote:
>>SetEnv force-response-1.0
>>
>>According to the docs here:
>>http://httpd.apache.org/docs/env.html#special
>>The point of that was to deal with silly proxies that belched when they
>>saw "HTTP/1.1" (regardless of the actual protocol version of the
>>response).
> Really? I don't intuit that from the doc though you may be right. The behaviour being
> observed is how 1.3 has been working for years (pretty sure anyway) and to the best of my
> knowledge, it is not breaking anything. Would be interested in knowing what exactly is
> breaking with this PR.
I guess I'm reading that in the context of
http://httpd.apache.org/info/aol-http.html
and I'm also asking the question "What does force-response-1.0 do that
downgrade-1.0 doesn't do?"
And, indeed, I can get
HTTP/1.0 200 OK
Date: Mon, 22 Apr 2002 18:06:14 GMT
Server: Apache/1.3.20-dev (Unix)
Connection: close
Content-Type: text/html
out of an old Apache 1.3 I have hanging around. (Unfortunately, I don't
have a unix box with 2.0 right now, so I can't answer Will's original
question.)
But I agree, I don't see any need for that functionality in the modern
world, so perhaps it should just be removed.
Joshua.
Re: Can't force http 1.0
Posted by Bill Stoddard <bi...@wstoddard.com>.
> Bill Stoddard wrote:
> > 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.
>
> >>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.
>
> >>>http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8357
>
> I agree with you in regard to
>
> SetEnv force-no-vary
> SetEnv downgrade-1.0
>
> But the reporter is also using
>
> SetEnv force-response-1.0
>
> According to the docs here:
> http://httpd.apache.org/docs/env.html#special
> The point of that was to deal with silly proxies that belched when they
> saw "HTTP/1.1" (regardless of the actual protocol version of the
> response).
Really? I don't intuit that from the doc though you may be right. The behaviour being
observed is how 1.3 has been working for years (pretty sure anyway) and to the best of my
knowledge, it is not breaking anything. Would be interested in knowing what exactly is
breaking with this PR.
Bill
Re: Can't force http 1.0
Posted by Joshua Slive <jo...@slive.ca>.
Bill Stoddard wrote:
> 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.
>>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.
>>>http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8357
I agree with you in regard to
SetEnv force-no-vary
SetEnv downgrade-1.0
But the reporter is also using
SetEnv force-response-1.0
According to the docs here:
http://httpd.apache.org/docs/env.html#special
The point of that was to deal with silly proxies that belched when they
saw "HTTP/1.1" (regardless of the actual protocol version of the
response). So it should actually change the response line if it is to
work as documented.
Joshua.
Re: Can't force http 1.0
Posted by Bill Stoddard <bi...@wstoddard.com>.
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." <wr...@rowe-clan.net>
> To: "Developers" <de...@httpd.apache.org>
> 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.
> >
>
Re: Can't force http 1.0
Posted by Bill Stoddard <bi...@wstoddard.com>.
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." <wr...@rowe-clan.net>
To: "Developers" <de...@httpd.apache.org>
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.
>