Issue 43: Login with Google Account on Safari 3.2.1 stops on white screen
Status:  Released
Owner:
Closed:  Oct 2012
Reported by code-rev...@gtempaccount.com, Sep 24, 2009
Reported by Shawn Pearce <sop@google.com> on Tue Jan 27 13:02:15 PST 2009
Source: JIRA GERRIT-43
Affected Versions: 2.0, 2.0.1
Environment: Safari/3.2.1; Google Accounts OpenID

Trying to login with Safari 3.2.1 and Google Accounts OpenID fails.  After
clicking "Continue Sign-In" a white screen is shown inside the floating window
and no further activity happens.

The issue appears to be that the Google Accounts provider issues an HTTP
redirect back to Gerrit, making the browser use a GET request.  The payload of
the GET request is considered to be too large by Safari, as the Activity
window shows "request too large".

The other symptom I've seen is Safari shows the following error message:

  Safari can't open the page.

  ... because the network connection was reset, which sometimes occurs when
the server is busy.

I think the error message is wrong/confusing.  The server is my desktop
development system; an idle Jetty that works fine with Firefox and earlier
versions of Safari (e.g. Safari 3.1.2) are known to work.

I've asked Google Accounts folks to consider using HTTP POST here, but this
may also be a Safari bug.
Sep 24, 2009
#1 code-rev...@gtempaccount.com
Update by Shawn Pearce <sop@google.com> on Tue Jan 27 13:21:54 PST 2009

Change description to:
----
Trying to login with Safari 3.2.1 and Google Accounts OpenID fails.  After
clicking "Continue Sign-In" a white screen is shown inside the floating window
and no further activity happens.

The issue appears to be that the Google Accounts provider issues an HTTP
redirect back to Gerrit, making the browser use a GET request.  The payload of
the GET request is considered to be too large by Safari, as the Activity
window shows "request too large".

The other symptom I've seen is Safari shows the following error message:

  Safari can't open the page.

  ... because the network connection was reset, which sometimes occurs when
the server is busy.

I think the error message is wrong/confusing.  The server is my desktop
development system; an idle Jetty that works fine with Firefox and earlier
versions of Safari (e.g. Safari 3.1.2) are known to work.

I've asked Google Accounts folks to consider using HTTP POST here, but this
may also be a Safari bug.
----
Sep 24, 2009
#2 code-rev...@gtempaccount.com
Comment by Shawn Pearce <sop@google.com> on Mon Feb 16 08:59:30 PST 2009

This appears to be resolved.  I've been able to login fine with Safari 3.2.1
now.  I think Google Accounts may have done an upgrade which reduced the
length of the URLs.
Sep 24, 2009
#3 code-rev...@gtempaccount.com
Update by Shawn Pearce <sop@google.com> on Mon Feb 16 08:59:30 PST 2009
Status: Fixed
Sep 24, 2009
#4 code-rev...@gtempaccount.com
Comment by Shawn Pearce <sop@google.com> on Tue Mar 03 11:31:05 PST 2009

Looks to be a WebKit issue as it shows up in both Safari and Chrome.

Opened upstream:

  https://bugs.webkit.org/show_bug.cgi?id=24332
Sep 24, 2009
#5 code-rev...@gtempaccount.com
Update by Shawn Pearce <sop@google.com> on Tue Mar 03 11:31:05 PST 2009
Status: New
Sep 24, 2009
#6 code-rev...@gtempaccount.com
Comment by Shawn Pearce <sop@google.com> on Tue Mar 03 17:28:49 PST 2009

Fixed by:

  https://review.source.android.com/9059
  https://review.source.android.com/9060
Sep 24, 2009
#7 code-rev...@gtempaccount.com
Update by Shawn Pearce <sop@google.com> on Tue Mar 03 17:28:49 PST 2009

Fixed in version 2.0.6.
Status: Fixed
Sep 25, 2009
#8 code-rev...@gtempaccount.com
(No comment was entered for this change.)
Labels: FixedIn-2.0.6
Oct 25, 2012
#9 sop@google.com
(No comment was entered for this change.)
Status: Released