Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Več o tem

about:newtab no prewiew of gmx.de

  • 5 odgovorov
  • 1 ima to težavo
  • 4 ogledi
  • Zadnji odgovor od philipp

more options

I dont have a prewievimage of www.gmx.net in about:newtab.

All other sites create a Image, just gmx.de or gmx.net dont save the image. Its still white like i would never have entered the page.

I got this problem since 5 months in several Firefox- Release. Complete deinstallation with Userdata also do not make a change.

I dont have a prewievimage of www.gmx.net in about:newtab. All other sites create a Image, just gmx.de or gmx.net dont save the image. Its still white like i would never have entered the page. I got this problem since 5 months in several Firefox- Release. Complete deinstallation with Userdata also do not make a change.

Vsi odgovori (5)

more options

hello thevagrantd, in case this site is loaded via SSL (the url starts with https://) i think it is expected behaviour that no thumbnails are cached for security reasons...

more options

Hi madperson

thank you for you answer but the page is http://www.gmx.net/

more options

hello, here is a similar question and explanation: https://support.mozilla.org/questions/934776 i've looked at the non secure version of gmx.net again & it also sends the "no-store" header, so the site isn't supposed to be cached...

more options

ok thank you very much

maybe it is possible to create and store the cache by myself!?

more options

unfortunately there appears to be no workaround by mozilla at the moment, it is handled in bug# 756881