Closed Bug 1250065 Opened 10 years ago Closed 9 years ago

Append HTTPS automatically in the location bar while typing a remembered HTTPS connection, NOT HTTP

Categories

(Firefox :: Address Bar, defect, P2)

47 Branch
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: rakib.amin, Unassigned)

Details

(Whiteboard: [fxsearch])

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36 Steps to reproduce: 1. Type in https://yoursecuredomain.gTLD once. Bookmark it (optional) / visit it. 2. Do step 1 again, Firefox automatically brings it up the suggestion drop-down list. Hit enter. Actual results: Page Not Found/404 page is shown. Looking at the location bar, the url isn't "https://yoursecuredomain.gTLD". It's become http://yoursecuredomain.gTLD. Firefox didn't append https, it appended http. Expected results: Go to page https://yoursecuredomain.gTLD
Component: Untriaged → Location Bar
Priority: -- → P2
Whiteboard: [fxsearch]
I can't actually reproduce this. Firefox uses the https URL. Can you still reproduce? This is what I'm doing to be specific: 1. Start a new profile 2. Type https://example.com, hit Return 3. Open a new tab, close the old one 4. Type https://example.com (which is autofilled to have a trailing slash), hit Return Even if I type example.com in step 4 without the https, if I let it autofill and hit Return, it loads the https URL. But if I let it autofill and then delete the trailing autofilled slash and hit Return, then it loads http.
Flags: needinfo?(rakib.amin)
Hi, I have tested again in 47.0.1. The bug seems to be no more, goes to https://. I thought it was a cache update problem, like if you visit http://doman.com, and then they (doman) enables secure server login and then becomes https://doman.com, firefox doesn't update it. IT'S RESOLVED. Thanks for your time. And sorry for the inconvenience caused.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Flags: needinfo?(rakib.amin)
Resolution: --- → WORKSFORME
No problem at all, thanks for responding.
You need to log in before you can comment on or make changes to this bug.