Jump to content

Recommended Posts

Posted (edited)

Hi all,

 

 

Server: Version 3.0.5683.28609

Chrome: 44.0.2403.89 

 

 

Nothing major but when using emby over SSL gets put into mixed content mode and 100's of errors in dev console view.

 

was loaded over HTTPS, but requested an insecure font 'http://fonts.gstatic.com/s/roboto/v15/ek4gzZ-GeXAPcSbHtCeQI_esZW2xOQ-xsNqO47m55DA.woff2'.

 

google's recommendation is to load using https/ssl which will still work over http/non-ssl apparently. i don't know whether you've already noticed this or it's so trivial it's at the bottom of the list :-)

 

also discussed here:

http://stackoverflow.com/questions/24533912/loading-google-font-in-https-content-being-blocked

and here:

http://www.paulsodimu.co.uk/Post/Quick-Tip-Using-Google-Fonts-Over-HTTPS

 

Thanks for all your hard work and as always emby just gets better and better!!

 

P.s. it might be that i'm using url rewrite also and if so sorry for this post.

Edited by Rowlett
Posted

would it not be likely down to someone accidentally hard coding the protocol in the code (page), surely over https everything should be piped over https.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...