On Feb 19, 2005, at 11:02 AM, Arne Thomassen wrote:
But I disagree with your interpretation of the specification. 14.23
says
port number [...] as obtained from the original URI, and 3.2.2 says
If the port is empty or not given, port 80 is assumed. So the client
obtained the port number by
Hi,
I just tried it with telnet and can confirm the redirects, though
note that the redirect does not happen if you exclude the :80 or
:443 port information from Host.
It would appear that those sites have been configured to
canonicalize the URI used for access, and thus are directing
But I disagree with your interpretation of the specification. 14.23
says
port number [...] as obtained from the original URI, and 3.2.2 says
If the port is empty or not given, port 80 is assumed. So the client
obtained the port number by assuming that the standard port is
meant.
[Please CC: me on reply, I'm not subscribed to the list.]
Hi,
sometimes there seems to be a problem with the interoperation of the web
browser retawq (http://retawq.sourceforge.net/) and the Apache httpd -
the httpd sends a redirection response pointing back to the original
request URI, which
On Feb 18, 2005, at 4:51 PM, Arne Thomassen wrote:
sometimes there seems to be a problem with the interoperation of the
web
browser retawq (http://retawq.sourceforge.net/) and the Apache httpd
-
the httpd sends a redirection response pointing back to the original
request URI, which would cause
