hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 21216] - Redirect 302 to the same URL causes max redirects exception
Date Tue, 01 Jul 2003 17:41:44 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21216>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21216

Redirect 302 to the same URL causes max redirects exception





------- Additional Comments From christian.sell@netcologne.de  2003-07-01 17:41 -------
ok, heres the quote from section 10.3 in RFC 2616:

"A client SHOULD detect infinite redirection loops, since such loops generate
network traffic for each redirection. 
Note: previous versions of this specification recommended a maximum of five
redirections. Content developers should be aware that there might be clients
that implement such a fixed limitation."

To me, DETECTING an infinite loop is something else than limiting the number of
redirects, as the above remark about previous versions also confirms.

And, IMHO, multiple redirects to the same location == an infinite loop (unless
the resource at the location has changed in the meantime)

- I hope this issue does not get into an inifite loop ;-) -

Mime
View raw message