Hi all. I have noticed that google login redirect is something like this. <meta http-equiv="refresh" content="0; url='http://www.google.com/ .....> So generated redirect template looks like <table width='100%'><tr><td bgcolor='#ee0000'>Warning:</td> <td bgcolor='#8899aa' width='100%'> This page uses the NON-STANDARD meta refresh tag.<br> The HTML 4.01 SPEC (sec 7.4.4) recommends explicitly to avoid it.</td></tr> <tr><td bgcolor='#a0a0a0' colspan='2'>The author wanted you to go <a href=''http://www.google.com/ ... So dillo just navigates to the same page. This is the reason why we can't login. Regards, furaisanjin
furaisanjin wrote:
I have noticed that google login redirect is something like this.
<meta http-equiv="refresh" content="0; url='http://www.google.com/ .....>
So generated redirect template looks like
<table width='100%'><tr><td bgcolor='#ee0000'>Warning:</td> <td bgcolor='#8899aa' width='100%'> This page uses the NON-STANDARD meta refresh tag.<br> The HTML 4.01 SPEC (sec 7.4.4) recommends explicitly to avoid it.</td></tr> <tr><td bgcolor='#a0a0a0' colspan='2'>The author wanted you to go <a href=''http://www.google.com/ ...
So dillo just navigates to the same page. This is the reason why we can't login.
Does reloading work?
Does reloading work?
Do you mean redirecting? I modified html.cc like this. There is tailing single quotation mark but it seems that dillo ignores it. --- a/src/html.cc Sat Feb 14 10:14:38 2009 +0900 +++ b/src/html.cc Sat Feb 14 17:06:29 2009 +0900 @@ -2898,6 +2898,9 @@ /* Skip to anything after "URL=" */ while (*content && *(content++) != '=') ; + if (*content == '\'') + content++; + /* Send a custom HTML message. * TODO: This is a hairy hack, * It'd be much better to build a widget. */ now I can login by clicking "here". Regards, furaisanjin
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/ .....>
So generated redirect template looks like
<table width='100%'><tr><td bgcolor='#ee0000'>Warning:</td> <td bgcolor='#8899aa' width='100%'> This page uses the NON-STANDARD meta refresh tag.<br> The HTML 4.01 SPEC (sec 7.4.4) recommends explicitly to avoid it.</td></tr> <tr><td bgcolor='#a0a0a0' colspan='2'>The author wanted you to go <a href=''http://www.google.com/ ...
So dillo just navigates to the same page. This is the reason why we can't login.
The problem is that "content" in META can be anything. There's no format for it. It seems an heuristic may be of use here... What do you do to get that redirection? I've tried some google pages but can't get the ' -- Cheers Jorge.-
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. -- Cheers Jorge.-
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." [2] -- -- Rogut?s Sparnuotos
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.-
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/ .....>
So generated redirect template looks like
<table width='100%'><tr><td bgcolor='#ee0000'>Warning:</td> <td bgcolor='#8899aa' width='100%'> This page uses the NON-STANDARD meta refresh tag.<br> The HTML 4.01 SPEC (sec 7.4.4) recommends explicitly to avoid it.</td></tr> <tr><td bgcolor='#a0a0a0' colspan='2'>The author wanted you to go <a href=''http://www.google.com/ ...
So dillo just navigates to the same page. This is the reason why we can't login.
Just committed a patch for this. Please test. -- Cheers Jorge.-
participants (4)
-
corvid＠lavabit.com -
furaisanjin＠gmail.com -
jcid＠dillo.org -
rogutes＠googlemail.com