Recommended Posts

FYI: 0.6s to load for UK, on a reasonably fast ADSL connection; 1.4s to load at Amazon EC2 in Tokyo (but 0.04s on a 2nd try, so either Amazon cached it or the Japan or Asian CDN node needed to be initialized).

Share this post


Link to post
Share on other sites

Ok, it was not important that these changes be available right now, only that you know about them.  Only affects Oculus not working.

 

On SSL, I have bought and installed an SSL certificate in a web server as well a DNS name before.  I think the problem is how the server is being accessed.  The domain name used to access the server should match the name on the SSL cert installed in the webserver.

 

cdn.babylon.com is a DNS record pointing to a host, that whom ever manages babylon.com domain added.  Accessing the host via https using cdn.babylon.com should require that a multi-host capable SSL certificate for babylon.com be installed.  I have no idea what Azure is, but couldn't you access via https using a url that matched like "azure.com/.../babylon.js"?

Share this post


Link to post
Share on other sites

Hello David,

 

I'm sure the CDN is strong enough and pretty quick to respond everywhere in the world, my concern is to be able to call the script through SSL. Any plan to have SSL for the cdn.babylonjs.com host ?

Share this post


Link to post
Share on other sites

The problem is this one :

The server cdn.babylonjs.com delivers a (wildcard) certificate that validates another domain name : *.vo.msecdn.net

My DNS resolver tells me that cdn.babylonjs.com is a synonym (CNAME) of az612410.vo.msecnd.net

So https://az612410.vo.msecnd.net delivers thus a valid certificate under his name.

 

But there might be some incoming request name filtering or other rewrite rules because if you try :

https://az612410.vo.msecnd.net/2-1/babylon.js

you just get a 404 error :(

 

So whatever the server name, until there is no valid certificate matching the related domain name, you won't be able to get babylon.js file from a https connection.

This means you can't serve your own app under https if you want to reference this CDN (because browsers just want all resources winthin a html page to be from valid https if this page is under valid https)

Share this post


Link to post
Share on other sites

Vousk,

Are you planning on putting up "https://cdn.jsdelivr.net/babylonjs/2.2/babylon.min.js"?  I am trying to use this CDN for test scenes, in case I wish to publish them.  It cuts out a change step.  I use GoogleDrive for that & it is https.

 

Not testing anything that needs 2.2, nor publishing anything right now, just letting you know that I do use this CDN.

 

Thanks,

 

 

Jeff

Share this post


Link to post
Share on other sites

Hey JCP, nice to hear you,

When beta release concerned, I only put on CDN versions enough tested in production. But if you need, since I'm currently testing one particular 2.2 beta release on real prod environment cases with no particular problem, I can validate and publish it with confidence.

Share this post


Link to post
Share on other sites

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


  • Recently Browsing   0 members

    No registered users viewing this page.