Bug #1279
closed2013 Conference site: Missing stylesheet? (mixed content blocked, css/js offered via http when page accessed using https)
0%
Description
https://conference.libreoffice.org/2013/en
Looks like something's missing from that page, as it's rendering weirdly.
Files
Updated by Florian Effenberger almost 10 years ago
- Assignee set to Andreas Mantke
Andreas is most likely the one who can help us out here :)
Updated by Andreas Mantke almost 10 years ago
I can't See anything weird. Could you please explain Mord in Detail what went wrong. Maybe a screenshot with a Mark would do.
Updated by Andreas Mantke almost 10 years ago
Seemed to be an issue with Firefox and the Browser cache. IE 11 ISS fine here.
Updated by Florian Effenberger almost 10 years ago
Same problem with Chrome, Safari works. Possibly issues with the HTTPS,
you need to reference the CSS beginning with "//" or such to be
protocol-independent
Updated by Christian Lohmaier almost 10 years ago
- Subject changed from 2013 Conference site: Missing stylesheet? to 2013 Conference site: Missing stylesheet? (mixed content blocked, css/js offered via http when page accessed using https)
definitely the problem is with https - browsers refusing to load the insecure content unless its explicitly allowed (see the shield in chrome for example, or the corresponding messages in the web-developer tools/console, e.g.
Mixed Content: The page at 'https://conference.libreoffice.org/2013/en' was loaded over HTTPS, but requested an insecure stylesheet 'http://conference.libreoffice.org/2013/portal_css/tdf-conferencethememilano/base-cachekey-bc06f9a6a7f676dea69125b1c3e9abde.css'. This request has been blocked; the content must be served over HTTPS. en:31 Mixed Content: The page at 'https://conference.libreoffice.org/2013/en' was loaded over HTTPS, but requested an insecure stylesheet 'http://conference.libreoffice.org/2013/portal_css/tdf-conferencethememilano…ne.app.jquerytools.dateinput-cachekey-c95074ceaa1d85e8723aacf8914b7f1e.css'. This request has been blocked; the content must be served over HTTPS.
As Florian mentioned, protocol adjusting prefix (just "//" instad of "http://") will solve the problem.
(for the user, accessing the page using http also bypasses the problem)
Updated by Jean Spiteri almost 8 years ago
I can't reproduce this. Can it be closed?
Updated by Andreas Mantke almost 7 years ago
- Status changed from New to Closed
The site has been migrated to static html and I'm not responsible any more!