- From: Tu Yu-Guang <tuyuguan@comp.nus.edu.sg>
- Date: Tue, 25 Jan 2000 05:36:19 -0500 (EST)
- To: "Yves Lafon" <ylafon@w3.org>
- Cc: <www-jigsaw@w3.org>
> -----Original Message----- > From: Yves Lafon [mailto:ylafon@w3.org] > Sent: Tuesday, January 25, 2000 6:14 PM > To: Tu Yu-Guang > Cc: www-jigsaw@w3.org > Subject: Re: how to prevent the infinite http redirection > > > > Regarding redirections: > RFC2616: 10.3 > A client SHOULD detect infinite redirection loops, since such loops > generate network traffic for each redirection. > > And: > 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. > > Browsers are aware of that, no idea concerning some badly broken spiders > that may unfortunately exist. Thank you very much. I would like to confirm with you so that I can ensure that I understand you correctly. Do you mean the client browsers such as netscape or ie are taking care of detecting infinite redirection loops, so nothing needs to be done on the web server side? also the maximum of five redirections are implemented by the browsers? all latest version browsers support this? If the client are not able to detect it, what do you suggest to do? Thanks again, Yu Guang.
Received on Tuesday, 25 January 2000 05:38:19 UTC