491175 - endless loops loading gmail.com

Status: VERIFIED DUPLICATE of bug 430021

(Firefox :: General, defect)

Description

[bentnhaf]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10

trying log into my gmail account, the browser locks up into and endless loop trying to resolve the url

Reproducible: Always

Steps to Reproduce:
1. I log into my account from the login page...
https://www.google.com/accounts/ServiceLoginAuth?service=mail
2...which takes me my "Manage Account" page...
https://www.google.com/accounts/ManageAccount
3...but when I finally attempt to actually get to the gui that allows me to use the account by clicking on the link...
http://mail.google.com/mail?hl=en
4...it goes into an endless loop. I have to kill the window, open up ie. which does not lock up in this process and allows me to access my gmail account.
Actual Results:  
...see the above "Steps to Reproduce" where I detail the results.

Expected Results:  
...see the above "Steps to Reproduce" where I detail the results and expected results.

I saw several other bug reports with this exact same problems that my version has for earlier firefox versions and claims that gmail solved some things on their end that supposedly fixed their problem.  Not mine.

Comment 1

[rsx11m]

Did you follow the discussions and suggested steps in bug 430021?
This has been linked to cookie issues or http versus https access.
Personally, I haven't seen it for a couple of months now.

Comment 2

[bentnhaf]

From comment #1, my problem is solved after extensive reading of bug 430021 and specifically, its comment #25 relating to the need to allow cookies.

This now boils down to a privacy issue and an incredible disregard to customer service by gmail and google. Google's malfeasance is seen by comparing their customer regard to other domain sites that require cookies...who if they haven't said up front that you have to engage cookies in order to use their site; actually have the courtesy to throw up an error message when detecting the loop behavior of a logon attempt advising as such.  The privacy issue is inherent to the whole concept of cookies themselves.  Where do you draw the line?  This part of the discussion is not gist for this mill at mozilla, I s'pose, except to say that it was only necessary to allow session cookies for the problem to be solved, not permanent cookies, in my case.

However, this disregard is further acknowledged by the study of the current 32 comments in 430021 showing that this behavior has been manifest at least as far back as firefox v2.0.0.13 and seamonkey v1.1.9. Its not determined from any of this discussion whether the look at themes could have been undermined by this cookie issue.

I attempted to apprise gmail/google of my idea to get on board with my customer service suggestion but nowhere on their site could I find a venue to add a new issue.  I could only 'view and report' which was little more than placing another chalk mark next to the 'gmail load looping' issue.

This issue should not be closed, here or anywhere else, till consumers no longer have to spend hours discovering their private little fix, as you and I have.  If the powers that be think otherwise, then I hope the last comment entered here will lead the way to properly addressing this customer service issue.

Comment 3

[bentnhaf]

...2nd line above, comment should have been entered as comment 430021#25...

Comment 4

[bentnhaf]

I don't know what I'm doing here with my attempt to edit...someone who can, delete this and #3 above and then go to bug 430021 and delete my duplicate # 34 there.

thanx.

Comment 5

[bentnhaf]

...and then, show me the tutorial that will tell me how to not make these mistakes...and show me how to engage appropriate key words I tried to enter that wouldn't stay.  I thought, "gmail_looping firefox seamonkey cookies" would be appropriate but none of them stayed.  Am looking for these answers on my own in the mean time.

Comment 6

[Tanner M. Young [:tmyoung]]

I have file Bug 496588 for support documentation to be written about this issue, and I have CCed benthaf.

I am resolving this Bug as a Duplicate of Bug 430021.

Comment 7

[Aakash Desai [:aakashd]]

The bug's are one in the same and 430021 was created before this one.