Not exactly what I said ;-)
I said that irrespective to what RFC could imply, some sites intentionally
use redirection to the same location, and the site (server) should normally
prevent endless looping. If it's not, than indeed a client should protect itself
- whether it is implemented in HttpProt or outside. Other fields of http-header
except Location should be also considered for proper loop detection.
For example, the URL checker should accept and preserve cookies
between requests and alert looping only if cookies do not change.
It is not clear to me from the spec, but if it makes the express assertion that it "SHOULD" give the new URI in the response to
non-HEAD requests, by omission it seems to me that it then "MUST" do so for HEAD.
Either way, I wouldn't rely on a URI being given, ever. Like Stan said, it is
up to the client to avoid loops.
dZ.
--
DZ-Jay [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
--
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
