RFC says that Location can contain only absolute URI.
Wikipedia say, that some software allows for relative URIs, but in that case
they must start from leading slash. So the response of the given server seems
incorrect. So http client may handle such malform relocations using its
arbitrary custom implementation.
Best wishes,
Stan
----- Original Message -----
From: "Angus Robertson - Magenta Systems Ltd" <an...@magsys.co.uk>
To: <twsocket@elists.org>
Sent: Friday, November 30, 2012 7:13 PM
Subject: [twsocket] HTTP relocation
= Connected to: www.cytauk.com
GET / HTTP/1.0
Host: www.cytauk.com
< HTTP/1.1 302 Moved Temporarily
< Location: ./cytauk2/
= Connected to: www.cytauk.com
GET /./cytauk2/ HTTP/1.0
Host: www.cytauk.com
< HTTP/1.1 404 Not Found
Firefox seems to redirect to www.cytauk.com/cytauk2/ ignoring the extra ./
in the relocation header.
Is the server wrong, Firefox too forgiving, or do we need a fix?
Angus
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
