On Sat, Feb 14, 2009 at 05:22:54PM +0200, Rogut??s Sparnuotos wrote:
Jorge Arellano Cid (2009-02-14 11:35):
On Sat, Feb 14, 2009 at 03:44:49PM +0900, furaisanjin wrote:
Hi all.
I have noticed that google login redirect is something like this.
<meta http-equiv="refresh" content="0; url='http://www.google.com/ .....>
BTW, does anybody know why some sites are using a refresh with delay zero?
I also saw this technique used in gitweb, but don't know what problem it is suppossed to solve.
I think that * it is used as a supplement to server-side redirect (the Location: header) * instead of server-side redirect (whatever the reasons [1])
In both cases, the user is not supposed to see the redirect happening, as it is happening for technical (and not necessarily clever) reasons.
I might be totally wrong, but these are the impressions I got while investigating how to redirect the user to another page after a successful POST (so the data is not submitted again in case of a client-side page refresh).
[1] Following the link, there is this sentence: http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G110.html
"However, authors do not always have control over server-side technologies; in that case, they can use a client-side redirect."
Thanks a lot for the useful information! It seems like w3c decided to tolerate META refresh when the delay is zero. i.e. "instant client-side redirect". That explains its usage. OK, I'll work on a patch for this and the related bug that furaisanjin wrote (W3C's example uses a quoted URL). -- Cheers Jorge.-