[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: meta refresh delay 0 looping
- From: Kevin Ryde <user42_kevin@xxxxxxxxxxxx>
- Date: Sat, 09 May 2015 12:18:55 +1000
- X-ml-name: emacs-w3m
- X-mail-count: 12447
- References: <878uczltgg.fsf@xxxxxxxxx> <b4m7fsj38re.fsf@xxxxxxx>
Katsumi Yamaoka <yamaoka@xxxxxxx> writes:
(B> I think the problem in this case is that the url is its own.
(B> It will never happen normally, doesn't it? However, the Google
(B> case is serious.
(BI think google is giving that, the same url unchanged as the target.
(B> Could you see my article posted just before?
(BMail crossing :).
(BFor your hack maybe don't follow delay 0 refresh if the same target url
(Balready, since that would be an infinite loop (unless the server
(Battempts stupid games of varying content).
(BI wondered if delay 0 refresh might count against the
(B`w3m-follow-redirection' limit. That could limit potential abuse, and
(Bsupposedly in the dim dark past delay 0 was sometimes mis-used by
(Bauthors instead of "301 Moved", the two ways being substantially similar
(Bif the browser obeys.