Closed Bug 487403 Opened 16 years ago Closed 16 years ago

Can't browse to SSL sites after clearing private data (specifically, "authenticated sessions")

Categories

(Core :: Networking, defect)

defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 480619

People

(Reporter: support, Unassigned)

References

()

Details

(Keywords: qawanted)

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1 (.NET CLR 3.5.30729) The short description of the problem is that we have a web page the loads fine everywhere but in the brand new release of Firefox.. 3.0.8, and then only on PC (works find on Macs). We don't know if it is some sort of SSL handshake problem.. but that is our current suspician. This is a very high priority problem for us... our sales have suddently dropped 30% right after Firefox 3.0.8 came out. Reproducible: Always Steps to Reproduce: http://www.bottomlinesecrets.com/store/mags/order_test_mag.html Actual Results: people in FF 3.0.8 are not able to view the site https://www.bottomlinesecrets.com/store/mags/order_ths_cert.html Expected Results: https://www.bottomlinesecrets.com/store/mags/order_ths_cert.html resolves
I have been never on your page, opened the https page and it worked fine in Seamonkey 1.9.1 branch and Firefox 3.0.8 (1.9.0 branch). I get the issue only if i clear the disk cache+sessions and doesn't restart Firefox but that should not explain your issue with dropped sellings because why should people clear cache before they visit your page ? this looks like a dupe of bug 480619
Status: UNCONFIRMED → NEW
Component: General → Networking
Ever confirmed: true
Flags: blocking1.9.0.10?
Product: Firefox → Core
QA Contact: general → networking
Version: unspecified → 1.9.0 Branch
I don't see anything obvious that would've caused this specifically in Firefox 3.0.8 (we only fixed two bugs in that version). Johnath: Any comment on this or why it'd change suddenly?
None, really - and I can't reproduce it (albeit on Mac). The only thing I see is some malformed XML errors in the error console, but they don't stop the page from rendering for me. Is it possible the website changed around the same time? Not trying to shift blame, just trying to understand what's causing the behaviour you're describing. The bugs fixed for 3.0.8 compared to 3.0.7 should not have caused any SSL-related changes to this site.
Blocking 3.0.10 if people really can't get to your site due to a 3.0.8 change, but that seems extremely unlikely: QAWanted. This may not be blocking if it's older bug 480619, but that seems unlikely to account for such a huge drop.
Flags: blocking1.9.0.10? → blocking1.9.0.10+
Hello, I'm not entirely sure which technician on our end opened up this issue, but it is definitely not an issue. I have now verified an installed version of FireFox 3.0.8 at two separate locations. I have ensured my cache and everything was cleared and attempted the link, both of which worked fine and without delay or error. I appreciate the work done on this ticket, but this definitely looks as though this was something that was on our end that was preventing the https connection, because there should be no reason that the SSL stopped working from version 3.0.7 to 3.0.8, as there was nothing at ALL related to SSL's that was changed. Thank you
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Thanks for following up!
Flags: blocking1.9.0.10+
I can still see the issue with FF3.0.8 on windows 2003 without addons / test profile). If there would be something wrong with the SSL connection you would get an error but Firefox doesn't seem to load the page (the spinner doesn't animate). Steps to reproduce : load http://www.bottomlinesecrets.com/store/mags/order_test_mag.html, click the link to the ssl page, click back, clear browser cache+sessions. Sometimes it works and sometimes Firefox doesn't react to the clicked link. Just load forward and backward and clear the cache/session/history. That is however not that important to block a release.... Could you check this on a win32 build Samuel ?
Yes. I definitely see that. As a matter of fact, here's clear instructions for this bug, which I'm reopening and throwing the blocking1.9.1? flag at. STR: 1. Open Firefox 3.0.8 (also tested latest Shiretoko nightly) with a clean profile 2. Go to google.com 3. Press the "Sign In" link in the top right 4. Go back 5. Go to Tools -> Clear Private Data and select *only* "Authenticated Sessions" then press "Clear Private Data Now" 5b. For Shiretoko, it's Tools -> Clear Recent History with "Active Logins" checked 6. Press "Sign In" once. ER: Load the Sign In page for Google Accounts. AR: Nothing. Very, very weird... If you push the Sign In link enough, eventually it'll load. I can reproduce this on Mac (tested Shiretoko) and Windows (tested 3.0.8). Matti: Thanks for pressing me on this bug.
Status: RESOLVED → REOPENED
Flags: wanted1.9.0.x?
Flags: blocking1.9.1?
OS: Windows XP → All
Hardware: x86 → All
Resolution: WORKSFORME → ---
Version: 1.9.0 Branch → Trunk
Summary: SSL not being seen by store in Firefox 3.0.8 → Can't browse to SSL sites after clearing private data (specifically, "authenticated sessions")
Note: I think this is different from bug 480619 because, in that case, only certain parts of the page won't load (images, CSS, etc) whereas in this case, you can't even click and make it to the site.
I was able to reproduce this using the latest 1.9.1 nightly on Windows Vista and visiting igoogle.com. I have not yet been able to repro this using Mac.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.8) Gecko/2009032609 Firefox/3.0.8 (.NET CLR 3.5.30729) This is the http log I get while following the steps in comment #8.
This is not a regression. The bug as described in comment 8 exists as long as the possibility to clear SSL sessions exists (since 2005).
Status: REOPENED → RESOLVED
Closed: 16 years ago16 years ago
Resolution: --- → DUPLICATE
Flags: blocking1.9.1? → blocking1.9.1-
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: