[x3d-public] Constraints on X3D within X3DOM

[Leonard Daly]

Hi Anthony,

There is a problem with cross-site scripting.
In the version you linked 
(https://www.laetusinpraesens.org/x3dom/mandala_concord.html), Firefox 
generates the error "Cross-Origin Request Blocked: The Same Origin 
Policy disallows reading the remote resource at 
https://laetusinpraesens.org/docs10s/images/helixtor_files/helix_24_rot.x3d. 
(Reason: CORS header ‘Access-Control-Allow-Origin’ missing)."

The referenced X3D file is accessed on a different domain that the base 
content ("www.laetusinpraesens.org" is not the same as 
"laetusinpraesens.org").

If you change the base page URL to 
https://laetusinpraesens.org/x3dom/mandala_concord.html, then the 
colored pentagram helixes show.

Alternatively, you can include a CORS header. See 
https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSMissingAllowOrigin 
for more information.

Leoanrd Daly



> I have successfully produced relatively complex models with multiple
> ROUTES in X3DOM as with:
>
> https://www.laetusinpraesens.org/x3dom/saha_crown_gyro.html
>
> The key being to avoid PROTO statements.
>
> I am stymied by the constraints with another model (working locally in
> H3Dviewer)  for which I get an "unsupported protocol" message, as for:
>
> https://www.laetusinpraesens.org/x3dom/mandala_concord.html
>
> Any checklist?  Any clues? Too complex?
>

-- 
*Leonard Daly*
3D Systems & Cloud Consultant
LA ACM SIGGRAPH Past Chair
President, Daly Realism - /Creating the Future/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20200519/98719cb5/attachment.html>