I'm using Firefox, and while setting up a server, I have been fiddling around with redirects. Now, Firefox has cached a 301 redirect from http://example.com/ to https://example.com/ and from http://sub.example.com/ to https://sub.example.com/.
I've tried the following things:
History -> Show all history -> Forget about this site.
Checked that no bookmark with https://example.com/ is present.
Changing browser.urlbar.autoFill to false in about:config.
Changing browser.cache.check_doc_frequency from 3 to 1.
Options -> Advanced -> Network -> Chached Web Content -> Clear now.
None of the above works, so I checked the redirect with wheregoes.com and it doesn't show any redirect from http to https.
I've even changed the DNS to point to another IP served by a server, where I've never set up redirection - the redirection is still in effect.
I've also tried in Private Browsing in Firefox, and there is no redirect there. I've tried in Google Chrome, and there is also no redirect here.
I've also tried to make a redirect from https to http which worked in Google Chrome, and yielded a redirection error in Firefox.
My version of Firefox is 38.0.1, and I'm using Windows 8.1. I use the following addons: AddBlock, Avast! and LastPass. Avast! may not be the issue, as I've disabled it while testing.
What I can do about it?
"Sites preferences" are the culprit. Wasted 45min of my life finding how to fix it despite all the kb/support.mozilla tricks which does not solve your issue nor did mine. I don't know what triggers this issue, but several of my websites started to go pear-shaped in a few weeks only affecting me and only firefox.
That's the solution you are all looking for:
Go to Preferences
Privacy
Click 'Clear your history' (nothing will happen yet, click safely)
Once the pop-up appears, click Details.
Untick everything except 'Sites Preferences'
Select 'Everything' in the select box at the top
Click Ok
Try now
PS: What I did try that did not worked for me are:
urlbar.autofill false
Forget Website trick
Safe mode
We all know it is not an HSTS issue when a website you own and you accessed before never got https support but now FF wants you to use https... It is just a firefox bug IMO.
The solution that worked for me:
Go to about:config
Look for network.stricttransportsecurity.preloadlist and set it to false
Enjoy
If the above STILL DOES NOT WORK, try setting browser.fixup.fallback-to-https to false from about:config
Using Firefox 100 or above you may also need:
dom.security.https_first to false
dom.security.https_first_pbm to false (this one is for anonymous windows)
I had the same problem but the answer was that I used a .dev extension to access my local websites !
I cleared all historic data in FF and nothing changed.
Searching for another solution, I found this page https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts/
With .dev being an official gTLD, we're most likely better of changing our preferred local development suffix from .dev to something else. If you're looking for a quick "search and replace" alternative for existing setups, consider the .test gTLD, which is a reserved name by IETF for testing (or development) purposes.
I changed my local website extensions from .dev to .test and all work perfectly !
Alternative solution, easy.
Open Firefox and in the address bar type this URL
http://example.com/?fake_parameter_to_bypass_cache
This should force the browser to reload the web page from http://
None of the answers worked for me, the only the one was the one in the comment of Muhammad so thanks in advance to him, I copy the answer here to make it easier:
Go to about:config
Look for browser.fixup.fallback-to-https and set it to false
Check your extensions!
In my case, DuckDuckGo Privacy Essentials extension was causing this redirect. I disabled it, and the problem is solved.
Now (Firefox 84) it is much simpler to clear the site's data. Just click the padlock icon on the left of the address bar. Then choose "Clear cookies and site data".
I had the same situation as what OP did. It helped me to clear the HTTPS redirect.
Here's what worked for me on Firefox v98.0.2:
Settings -> General
Network Settings -> Settings
Uncheck "Enable DNS over HTTPS
I tried the 'correct' answer, plus the comment about including cache in the deletion, and I was still having issues with my problem site.
I opened the firefox profile directory and searched for the website name in all files.
I found it in 'logins-backup.json' and deleted that file to finally fix the problem.
In my case, I decided to use a *.dev domain for local development. But then I tried to open the site in Firefox, and after a while I realized it uses HTTPS, even when I start the url with "http://..." I tried to right-click on the link in the History, and choose Forget About This Site, or clear the cache. But it didn't help.
Later I found out that the dev domain is in HSTS preload list these days. Which means Firefox and Chrome (and probably others) don't let you access the subdomains w/o HTTPS. More on it here and here.
In my case, it was an addon that did it: disabling DuckDuckGo privacy essentials fixed it.
I had this issue when running Firefox with OWASP ZAP proxy.
I didn't knew it was the proxy causing this.
In hindsight it's easy to test this: run Firefox without OWASP ZAP proxy to see if it works.
To get it working with OWASP ZAP, turn off Heads Up Display (HUD) or enable the HUD only for URL's that are in scope.
My problem was caused by the HTTPS by default extension. There is a bug that opens HTTP bookmarks with HTTPS. To work around, open "HTTPS by default" Preferences pane and enter domain name exclusion.
None of these suggestions worked for me in Firefox v101. What worked for me is changing the value of security.tls.version.min from 3 to 1 in about:config.
[NOTE: After I changed this setting, Firefox initially redirected from http to https. But this time Firefox allowed me to "accept the risk and continue," which wasn't possible when security.tls.version.min was set to 3. --end note]
See also: https://support.mozilla.org/en-US/questions/1116550
Lets get back to the old firefox that was amazing, the 3.6.
Nowadays is full of crap for us developers, and sysadmins.
I have tons of sites in intranet that cannot have a valid ssl, this is a major deal. I cannot download "deb" files because its a threat, i cannot this and cannot that... why? I am a power user i know what to do whit, why should I (we) be treated like the rest of the users?
The cache, i cannot disable the cache to 100% why?
In a blip of a second i will be using links as my browser.
Firefox should have a expert mode, where none of this crap happens.
I am mad with firefox and chrome. That is why i still use firefox 3.6 in a lot of cases, to bypass stupid restrictions.
Now, I had this issue on my workstation's development site. I had an old site that I still wanted to reference, and I couldn't get http to work for anything. There was not https binding, either.
Finally, I realized I had a url-rewrite in my webconfig that redirected all http to https...
hahahaha
Disabling https, is not an absolute in Firefox. Some sites will redirect and may not offer http.
However to choose one url over the other if it is an option you can disable autofil:
Address Bar Search In order to change your Firefox Configuration please do the following steps :
In the Location bar, type about:config and press Enter. The about:config "This might void your warranty!" warning page may appear.
Click I'll be careful, I promise! to continue to the about:config page.
In the filter box, type or paste autofill and pause while the list is filtered
Double-click browser.urlbar.autoFill to toggle it from true to false.
I get this error on Firefox 24.0, and I have firebug, fireftp and colorzilla installed. This just started happening recently. I have searched for this problem but all the topics come up as being from 2-4 years back, mostly Firefox versions 3 through 4.
Anyone have an idea how to fix this? They work in IE OK.
This also appears to do this for the main list page:
https://drive.google.com/?pli=1&authuser=0#
that just hangs without showing ANY of my docs.
I struggled with this for weeks.
Finally what resolved it is pretty stupid... Not sure if it will work again.
But maybe it will help someone!
Instead of going to drive.google.com I just opened docs.google.com and after it forwarded me to drive everything started to work... without even a cache clean!
Pretty funny!?
I have an April fools prank in mind and I will probably need some time to figure it out, so that's why I'm early:
I want to install an extension in the browser (needs to target botch FF and IE, so a cross browser implementation would be best) of my friend so that if he hits the news page he is visiting every morning, a fake image will make him think that he has been selected. The problem is, that I cannot just swap the images. I have to use the actual image from that website and put his head on the body of someone else.
I do have some graphics guys that can do that sort of stuff. My problem over here is to hook into the rendering process and do my own alterations to the image before it gets rendered. That is, taking the image, doing stuff to it and then passing in the modified image to the browser so that it is being redered instead of the original one.
Is that possible using extensions? If it may be only possible with eihter FF or IE, I might get him to use the browser of choice but I'd highly appreciate your suggestions, code snippets and starting points for research. Are there browser extensions that can do similar stuff?
Cheers everyone. There is a lot of reputation in that game so I don't care if it takes weeks or even months to complete the job.
Thank you guys, looking forward to suggestions!
Max
I think your intentions are harmless, but I must warn you: not all people may find your prank funny. But if you are sure that your friend will enjoy such a prank, it's really easy to set up.
You can use BFilter with site-specific filter to replace the image URL (it is very easy, just look at its examples and documentation). So when the user tries to open the web-page he will see your image instead of original picture. BFilter can be used as transparent proxy. I do not know how to setup transparent proxy in Windows, so you have to figure this part yourself. Alternatively, you can configure all installed browsers to use your filtering proxy.
You can use any other filtering proxy instead of BFilter.
I use Selenium to test my website. The website need to access an external catalog to select some items from it. The problem is this catalog is published on another domain with HTTPS protocol. I've searched and read many topics on the internet about Selenium and Cross domain problems, but I still don't find the answer yet. Some topics said that the *iehta browser will overcome this issue, but in fact it could not do that. I also try *iexplore, *iexploreproxy, *firefox, *firefoxproxy as well, but the results are the same. Could you please give me the solution for this problem?
Thanks in advance!
I've used the -trustAllSSLCertificates option with success.
Go to the site first with a normal IE connection, you get the message:
There is a problem with this website's security certificate.
Then:
Click Continue to this website (not recommended).
You'll see there's a red "Certificate Error" box at the top of the browser.
Click that, click "View Cetificates" then "Add" and add the certificate to the "Trusted Root Certification Authorities". There are similar screenshots for this process in the "mogotest" link in the previous answer.
Now run Selenium with the -trustAllSSLCertificates option and you are away.
The *iexplore (HTA mode) and *firefox (chrome mode) launchers will work just fine. *googlechrome will work in the forthcoming 2.0 release. As for the mechanics of making SSL work, the following article may help:
http://mogotest.com/blog/2010/04/13/how-to-accept-self-signed-ssl-certificates-in-selenium
Is there some sort of profiling tool available? View source and search/replace?
Although the message is usually a problem in IE, loading the page in Firefox with Firebug will let you see what is going on.
Also, you might find it helpful to leave the protocol off of the URLs in the first place: Http-https transitions and relative URLs.
I used view source which helps, although you might want to get a tool that lets you see the current source of the page like firebug in firefox.
One thing I ran into where this didn't help is if you have an iFrame in IE6 without a src attribute. IE6 will warn you about mixed content. No ammount of viewing source helped with this.
Edit
Not sure why I didn't suggest this but you try using Fiddler? Or another packet sniffer? This should let you see ssl traffic, which might help you narrow it down.
WireShark may also be of some help if you want something besides Fiddler, Firebug or HttpWatch for tools to try to resolve the issue.