Closed
Bug 1334339
Opened 8 years ago
Closed 8 years ago
Connection not secure - AOL web Mail
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: u212676, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20170124094647
Steps to reproduce:
Selected mail from my AOL Home Page
Actual results:
AOL opens a new window for Web Mail.
Clicking on Log-in field opens drop down of ID's associated with AOL Mail.
Fire Fox 52.0b1 reports that the connection is not secure (URL begins with HTTPS:)
FF issues this message: "This Connection is not secured" "Logins entered here could be compromised"
Expected results:
New message never seen before.
While I understand the meaning of the message, I don't see how I can fix this myself.
Suspect certificates for AOL are out of date?
I don't see a new window when clicking on the webmail link of AOL, it goes to https://mail.aol.com/
Could you provide the link top open the mail?
Flags: needinfo?(bpilkey)
First: AOL re-directs ques to AOL.com based on your IP Address. I can't get to AOL.com because it re-directs to AOL.ca.
Starting URL: http://www.aol.ca/ (I do not log into this page, it is my default home page). Click on the mail icon: - In my browser it opens a new browser for some reason:
Mail Starting URL: https://my.screenname.aol.com/_cqr/login/login.psp?sitedomain=sns.mail.aol.com&seamless=novl&lang=en&locale=CA&authLev=0&siteState=sid%3A2e0d8499-63d1-4794-95ce-66dbfeabe604%7Cqp%3A%7Cld%3Amail.aol.ca%7Cuv%3AAOL%7Cat%3ASNS%7Clc%3Aen_CA%7Crt%3ASTD%7Csnt%3AScreenName%7C&offerId=webmail-en-ca
NOTES: 1. System time date are correct
2. I run Panda Virus, but I do not believe it scans SSL connections
3. I have two other browsers FF 51.0 running on two Win 10 platforms without issue
4. I tried copying the profile from one of these machines running FF version 51.0 and renaming the affected profile as "Old". This worked once (that is, it did not give a warning initially), but after that when FF closed and re-opened it provided the warning.
5. This certificate problem appears to be related to version 52.0b1 updating early yesterday morning.
Do you need screen shots? Please advise.
Flags: needinfo?(bpilkey)
I got tired of trying to figure out what happened to FF during it's last download / update to 52.0b1 a few days ago.
Rolled it back to version 51.0.1 and there are no issues with secure layer transport.
Something happened during the update of 52.0b1 - that, I am convinced.
None of our other platforms have FF browser issues either as they are running 51.0 as well.
I consider 52.0b1 unstable and for this reason have opted out of the Beta channel.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
I can't reproduce it with Nightly. The AOL mail is open in the same tab, not in a new browser window.
And the URL of the login page https://my.screenname.aol.com/_cqr/login/login.psp is completely secure, see my screenshot: http://i.imgur.com/wgk57MU.jpg
Not sure why you are chasing this after I closed it; - too prove some nebulous point that clearly is not founded unless you can duplicate my experience.
I offered screen shots, but no one requested them. In my court of popular opinion that makes any analysis done into this problem more of a Witch hunt than true discovery to see what might be wrong.
I have little patience for stupidity, and even less for those who don't look beyond what they can see.
Mine showed a secure page too under 52.0b1, but when the next window opened (also denoted as secure) and ID drop down appeared the browser showed the message I have already documented insisting that the page was not secure, probably because it clobbered the certificates somehow during the update to 52.0b1.
Whether it is in one browser tab/window or two is inconsequential. You've missed the point entirely of my original bug entry - SOMETHING ISN'T WORKING CORRECTLY.
Enough! Go find someone else to bench test your Beta software for FREE.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago → 8 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•