Direct reference of file locations

Looks like this only works if load=<relative_path>, where the file is also on the cdn.soft8soft.com server. Web browsers throw an error when I try load=<url_path>, such as load=https://mywebsite.com/chemical-id/example.gltf. This is blocked because it is a cross-origin request, which looks to be flagged as a security issue.

Here’s the html error:

Access to XMLHttpRequest at ‘http://mywebsite.com/chemical-id/chemical.gltf&#8217; from origin ‘https://cdn.soft8soft.com&#8217; has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.

There’s also a warning on the webpage:

A cookie associated with a cross-site resource at http://soft8soft.com/ was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure.

So maybe I just need to set up permissions correctly…? I’m not sure if that opens up security issues for my site though. It is probably better if I don’t combine locally made files with a CDN.

For three.js, loading a gltf looks pretty easy (see below). Is there an analogous command like v3d.GLTFLoader()?

var loader= new THREE.GLTFLoader();
loader.load(
  'http://mywebsite.com/chemical-id/chemical.gltf', 
  function(gltf) { scene.add(gltf.scene); },
  undefined, 
  function (error) { console.error(error); }
);

loadScene() is definitely the route to go! And I now have CORS request working properly.

For apps that I’ve made myself, I’ve also learned to manually set the variable sceneURL in order to indicate the <relative_path> or <url_path> — this would be line 13 in myexampleapp.js file. When using with Django, I found this to be a cleaner approach than adding ?load=<path> to the URL. It makes the urls cleaner and it is easier to script with Django’s templating system.

Thanks again for the help, Alexander and Yuri!

-Jack