[Tools-discuss] Re: Apache upgrade.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Tools-discuss] Re: Apache upgrade.



Henrik Levkowetz wrote:

> if you have further ideas, I'd be glad to hear them

New idea about the "document contains no data issue":  I started
with tools - html- rfc2298 getting this.  And a 404 for the same
query with "id" instead of "html".

Then I used www3.tools - html - rfc2298, and it worked.  It has a
link to 3798 (I wanted that number), clicking I got again the odd
"document contains no data", now for www3.tools - html - rfc3798.

At that point I figured that this issue is unrelated to tools vs.
www3.tools, but some ordinary timeout.  And testing that theory
by simply asking again for www3.tools - html - rfc3798 it worked.

And I recalled that we discussed this already months ago here, my
client sends a GET xyz HTTP/1.0, plus a Host: header field (older
clients are anyway doomed today).

Maybe it's an HTTP/1.1 303 vs. HTTP/1.0 302 issue.  Random test,
http://tools.ietf.org/html/rfc1357 (whatever, not 1234 :-), I got:

~~~ cut ~~~
HTTP/1.1 302 Found
Date: Fri, 17 Nov 2006 21:53:32 GMT
Server: Apache/2.2.3 (Debian) DAV/2 SVN/1.4.0 PHP/4.4.4-6 mod_perl/2.0.2 Perl/v5.8.8
Location: http://tools.ietf.org/html/rfc1357
Content-Length: 0
Connection: close
Content-Type: text/plain; charset=US-ASCII

~~~ end ~~~

Well, that document obviously is empty, and it redirects me to the
location I've asked for, is that sane ?  Testing it for a third time
(about a minute later) I get RFC 1357.

RFC 2616 says that a 302 SHOULD contain a short document with a link
to the new location, the content-length 0 violates that.  It also
says that clients SHOULD detect infinite loops, a redirection to the
URL I've asked for might not work as expected.

Frank



_______________________________________________
Tools-discuss mailing list
Tools-discuss at ietf.org
https://www1.ietf.org/mailman/listinfo/tools-discuss




Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.