Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Inconsistent HTTPS

  • 4 replies
  • 1 has this problem
  • 2 views
  • Last reply by davidm1

davidm1
davidm1
more options

I have a website with SSL. When I open it by simply www.sitename, FF automatically uses https and extends this to all sub-pages. When I open sub-pages directly, i.e. www.sitename/pagename, FF uses http and shows the insecure icon. If I open sub-pages with https://sitename/pagename, FF shows them as secure. Chrome and Edge automatically use https for sub-pages opened directly by www.sitename/pagename. Why is FF inconsistent in this way?

I have a website with SSL. When I open it by simply www.sitename, FF automatically uses https and extends this to all sub-pages. When I open sub-pages directly, i.e. www.sitename/pagename, FF uses http and shows the insecure icon. If I open sub-pages with https://sitename/pagename, FF shows them as secure. Chrome and Edge automatically use https for sub-pages opened directly by www.sitename/pagename. Why is FF inconsistent in this way?

All Replies (4)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Is the http:// protocol present in the source code for links if you check this via "View Page Source" in case you previously used http: on your web pages ?

You either need to use the https:// protocol or leave out https: and only keep the leading '//'.

  • //support.mozilla.org/en-US/questions/1305962

Modified by cor-el

davidm1
davidm1 Question owner
more options

Thank you cor-el for your reply but it does not directly address the problem, which is not related to a link to the page. To be more precise, if I simply type ixont.com/portfolio in the address field, FF shows the page as http and insecure while both Chrome and Edge use https and show the page as secure.

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 25 Contributor
more options

The first time I requested

www.ixont.com/portfolio (insecure)

the server sent a 301 redirect to

https://www.ixont.com/portfolio (secure)

But then every other request, I did not get that. So strange.

Neither Chrome nor old Edge redirected to HTTPS when I tested those after Firefox. Not sure what is going on.

How is the redirect set up?

davidm1
davidm1 Question owner
more options

To jscher2000, thank you for checking that. I don't know how redirect is set up. My ISP, iPage, has done that for me. I do have a little more information. I have FF 83.0 (64-bit) on an Ubuntu-Mate 18.04 and the same version on Windows 10. The problem occurs only in Windows. In Linux the redirect is HTTPS.