-
Notifications
You must be signed in to change notification settings - Fork 271
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need X3DOM HTTPS server to support https site. Otherwise, content is mixed. #650
Comments
I'd recommend using Let's encrypt to add https support on x3dom.com, it works well and it's out of beta now. |
I think the recommendation by FHG is to serve x3dom.css and x3dom-full.js from the same server as the web page. |
Yes, I downloaded the files. Now to update all my scripts :(. On Jul 11, 2016 4:27 PM, "Andreas Plesch" notifications@github.com wrote:
|
@cecilemuller That is something we really need. |
👍 I need this as well! |
Loading x3dom over HTTPS should work now ;) |
The HTTP to HTTPS redirection should also work now: |
Many examples now do not work from https://x3dom.org since they use http to load x3dom.js: |
The Tutorial & Example updating is already in progress. |
Tutorials are up to date. |
Thanks. |
Mixed Content: The page at 'https://www.carlsonsolutiondesign.com/X3DJSONLD/' was loaded over HTTPS, but requested an insecure stylesheet 'http://www.x3dom.org/download/1.7.1/x3dom.css'. This request has been blocked; the content must be served over HTTPS.
www.carlsonsolutiondesign.com/:1 Mixed Content: The page at 'https://www.carlsonsolutiondesign.com/X3DJSONLD/' was loaded over HTTPS, but requested an insecure script 'http://www.x3dom.org/download/1.7.1/x3dom-full.js'. This request has been blocked; the content must be served over HTTPS.
The text was updated successfully, but these errors were encountered: