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!

Vanwege onderhoudswerkzaamheden die uw ervaring zouden moeten verbeteren, heeft deze website beperkte functionaliteit. Als een artikel uw probleem niet verhelpt en u een vraag wilt stellen, kan onze ondersteuningsgemeenschap u helpen in @FirefoxSupport op Twitter en /r/firefox op Reddit.

Avatar for Username

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Firefox doesn't completly load certain pages when using https (SSL)

  • 1 antwoord
  • 1 heeft dit probleem
  • 21 weergaven
  • Laatste antwoord van cor-el

stigbye
stigbye
more options

I have installed a SSL certificate on my website, but have noticed a problem when loading certain pages having many elements (images) when using HTTPS (SSL) compared to using "regular" HTTP (non-SSL).

I have done some consecutive tests to show this problem, as shown below.

NOTE: I can reproduce this problem with the Norwegian version of the page used in the test, as the English version of that page (as selectable at the top of the page) is shorter and have too few elements (images) to reproduce the problem!

TEST 1 - using HTTP: Deleting all cached files and then load the following page: http://trafikksiden.motocross.io/informasjon/statens_vegvesen/faghandboker/gjeldende.html

Firefox start loading the page, and continue loading until the page is 100% completly loaded.

TEST 2 - using HTTPS: Deleting all cached files and then load the page: https://trafikksiden.motocross.io/informasjon/statens_vegvesen/faghandboker/gjeldende.html

Firefox start loading the page, but stop loading before the page is completly loaded, i.e. certain elements (images) has NOT been loaded.

By pressing F5, Firefox start reloading the page and then continue loading the remaining elements (images) until the page is 100% completly loaded.

TEST 3 - using HTTP (again): Deleting all cached files and then load the following page: http://trafikksiden.motocross.io/informasjon/statens_vegvesen/faghandboker/gjeldende.html

Firefox start loading the page, and continue loading until the page is 100% completly loaded.

TEST 4 - using HTTPS (again): Deleting all cached files and then load the page: https://trafikksiden.motocross.io/informasjon/statens_vegvesen/faghandboker/gjeldende.html

Firefox start loading the page, but stop loading before the page is completly loaded, i.e. certain elements (images) has NOT been loaded.

By pressing F5, Firefox start reloading the page and then continue loading the remaining elements (images) until the page is 100% completly loaded.

TEST 5 - using HTTP (once again): Deleting all cached files and then load the following page: http://trafikksiden.motocross.io/informasjon/statens_vegvesen/faghandboker/gjeldende.html

Firefox start loading the page, and continue loading until the page is 100% completly loaded.

As seen from the above, Firefox successfully load the page without any interruption when using HTTP ("http://..."), but NOT when simply changing to using HTTPS ("https://...")!

NOTICES:

1. When using HTTPS, the time in seconds before Firefox stop loading the page, and I then have to press F5 to continue loading the page and the remaining elements, do vary between each test!

2. When doing even more consecutive tests by switching between HTTP and HTTPS than shown above, Firefox do sometimes stop loading the page a second time, and then have to press F5 once again before the page is 100% completly loaded!

I have installed a SSL certificate on my website, but have noticed a problem when loading certain pages having many elements (images) when using HTTPS (SSL) compared to using "regular" HTTP (non-SSL). I have done some consecutive tests to show this problem, as shown below. NOTE: I can reproduce this problem with the Norwegian version of the page used in the test, as the English version of that page (as selectable at the top of the page) is shorter and have too few elements (images) to reproduce the problem! ------------------------------------------------------------ TEST 1 - using HTTP: Deleting all cached files and then load the following page: http://trafikksiden.motocross.io/informasjon/statens_vegvesen/faghandboker/gjeldende.html Firefox start loading the page, and continue loading until the page is 100% completly loaded. ------------------------------------------------------------ TEST 2 - using HTTPS: Deleting all cached files and then load the page: https://trafikksiden.motocross.io/informasjon/statens_vegvesen/faghandboker/gjeldende.html Firefox start loading the page, but stop loading before the page is completly loaded, i.e. certain elements (images) has NOT been loaded. By pressing F5, Firefox start reloading the page and then continue loading the remaining elements (images) until the page is 100% completly loaded. ------------------------------------------------------------ TEST 3 - using HTTP (again): Deleting all cached files and then load the following page: http://trafikksiden.motocross.io/informasjon/statens_vegvesen/faghandboker/gjeldende.html Firefox start loading the page, and continue loading until the page is 100% completly loaded. ------------------------------------------------------------ TEST 4 - using HTTPS (again): Deleting all cached files and then load the page: https://trafikksiden.motocross.io/informasjon/statens_vegvesen/faghandboker/gjeldende.html Firefox start loading the page, but stop loading before the page is completly loaded, i.e. certain elements (images) has NOT been loaded. By pressing F5, Firefox start reloading the page and then continue loading the remaining elements (images) until the page is 100% completly loaded. ------------------------------------------------------------ TEST 5 - using HTTP (once again): Deleting all cached files and then load the following page: http://trafikksiden.motocross.io/informasjon/statens_vegvesen/faghandboker/gjeldende.html Firefox start loading the page, and continue loading until the page is 100% completly loaded. ------------------------------------------------------------ As seen from the above, Firefox successfully load the page without any interruption when using HTTP ("http://..."), but NOT when simply changing to using HTTPS ("https://...")! NOTICES: 1. When using HTTPS, the time in seconds before Firefox stop loading the page, and I then have to press F5 to continue loading the page and the remaining elements, do vary between each test! 2. When doing even more consecutive tests by switching between HTTP and HTTPS than shown above, Firefox do sometimes stop loading the page a second time, and then have to press F5 once again before the page is 100% completly loaded!

Bewerkt door stigbye op

Alle antwoorden (1)

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

No problems here with loading the HTTPS version of the page, all 144 images are loaded.

Did you use the Web Console and the Network Monitor to check for errors and the timings?

Did you check this in a clean profile?

If you use extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) that can block (wanted) content (Adblock Plus, NoScript, Disconnect, Ghostery, Privacy Badger, uBlock Origin) always make sure such extensions do not block (wanted) content.

Firefox shows the shield icon at the left end of the location/address bar in case Content Blocking is blocking content.

  • click the shield icon for more detail and possibly disable the protection

You can check the Web Console about what content is blocked

You can create a new profile to test if your current profile is causing the problem.

See "Creating a profile":

If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.