-
Notifications
You must be signed in to change notification settings - Fork 24
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
No 'Access-Control-Allow-Origin' header causes error in Linked Data Browser #83
Comments
@ahdinosaur - how do you get away with this re https://rawgit.com/valueflows/agent/master/examples/enspiral.jsonld ? I don't see any header there, either. P.S. looks like this might be what we need to do: @ahdinosaur @fosterlynn does this make sense to you, or is there a simpler method? I plead ignorance on this topic, but it looks like something we need to do post-haste for what we want to do here... Or @ahdinosaur - is it possible that your code is too strict? This is just a GET, right? |
yeah nah, this is expected. CORS headers are necessary for a browser to communicate with a server at a different domain then where the page was loaded. with here's a resource on how to enable CORS on servers. for example, here's how i added CORS support to our valueflo.ws |
@ahdinosaur - you're right, I was thinking stupidly about it. I think that django app will do it for us, but we'll see. |
Yay! It works now! @ahdinosaur and all: note that the URL has changed. I moved all the jsonld stuff under /api/ instead of /accounting/ |
We tried NRP jsonld error in @ahdinosaur 's Linked Data Browser
http://dinosaur.is/linked-data-browser/?focusId=http%3A%2F%2Fnrp.webfactional.com%2Faccounting%2Fagent-jsonld%2F
focus @id:
http://nrp.webfactional.com/accounting/agent-jsonld/
we get this error:
We'll add the required header. This issue is just to record the requirement. This is not a bug in the Linked Data Browser, just in the NRP jsonld feed. (Or so I think...)
The text was updated successfully, but these errors were encountered: