buffer.uri / image.uri validator accepting non-relative uri only, and not resources served over http(s)

Hi all,

Firstly, thank you very much for the plugin, it has made the workflow much much easier.

I was working with a project where binary resources easily adaptable to gltf format already exists and are served over https. After generating buffer.uri with values such as http://localhsot:3001/buffer, the validator complains about NON_RELATIVE_URI.

Is it an anti-pattern to serve buffer uri/image uri over http(s)?

coincidentally, gltf previewer, babylon.js does not load the buffer.uri served over http, but threejs does.

[lexaknyazev]

It’s not an anti-pattern per se, since the validator issues a warning, not an error. The reasoning is simple: not all clients will acquire external resources from URIs with explicit schemas (be it http:// or file://), so such assets are less portable. Of course, application-specific use cases for absolute URIs are valid.

As for babylon.js not loading resources over http, it may be an issue with VSCode plugin or Babylon.

/cc @emackey @bghgary

[bghgary]

Not sure why Three works and Babylon does not.

Babylon assumes urls are relative by default. It will not work with absolute urls without custom settings.