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.

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.

SVG doesn't work consistently. A site has https policy setup. If I open the page via https -- svg works. If I click link to same svg using http, it doesnt

  • 3 antwoorden
  • 3 hebben dit probleem
  • 4 weergaven
  • Laatste antwoord van longsonr

more options

Here is a demo link: https://www.doyourmath.com/t.html .

It works if you open the link. Inside it has link to same page but with http://. The https policy of the site forces FF to redirect http:// link to https://. After this -- SVG masks dont work, and nothing helps, even F5. Though the page and link is the same as first one.

Here is a demo link: https://www.doyourmath.com/t.html . It works if you open the link. Inside it has link to same page but with http://. The https policy of the site forces FF to redirect http:// link to https://. After this -- SVG masks dont work, and nothing helps, even F5. Though the page and link is the same as first one.

Alle antwoorden (3)

more options

I mean if you click a link in https://www.doyourmath.com/t.html , SVG is not rendered correctly anymore (though the page is exactly the same as originally).

I suspect that somehow during redirect from http:// to https:// svg-rendering-engine gets messed up.

more options

I see, the narrower block of red is correct, and wider block of red is incorrect.

If you right-click the link in the page and launch it in a new private window, Firefox doesn't "redirect" to HTTPS and it works fine. So the problem does seem to be tied to how Firefox implements Strict Transport Security.

I can't tell what's going wrong. I can't find any useful error messages, so better tools and/or deeper knowledge are needed. I suggest filing a bug on https://bugzilla.mozilla.org/

more options

This issue has been fixed from Firefox 45 onwards by https://bugzilla.mozilla.org/show_bug.cgi?id=1247733