Skip to content
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.

CORS proxy for parser #44

Open
antoniogarrote opened this issue Apr 13, 2017 · 1 comment
Open

CORS proxy for parser #44

antoniogarrote opened this issue Apr 13, 2017 · 1 comment
Assignees

Comments

@antoniogarrote
Copy link
Contributor

There's already a workaround for this.

I'm opening the issue for documentation and as a reminder of that we need a better solution.

Use of a proxy to resolve URL requests in the parsers is supported using a global variable.

window.JS_USE_PROXY = "http:/path.to/$URL"

Once this variable has been declared, requests will be send to the URL in the global variable where$URL is a placeholder for the position of the URL to request.
The URL does not need to be URL encoded. The library will take care of URL encoding it.

See this commit for more information: bb60502

Also check this commit in the AMF-playground to see how it can be enabled:

aml-org/playground@88bc420

@postatum
Copy link
Contributor

postatum commented Apr 13, 2017

Artem Kostiuk
@antonio.garrote regarding issues:
44(proxy) - not sure what I have to do about it. Is it just about defining JS_USE_PROXY in amf-playground if needed?
41(parsing error) - we already have a workaround and delay that for after Connect?
Antonio Garrote
Yes that's all. The variable is already added in the code of amf-playground, but is commented. See the last link in the issue. If you need to modify the request somehow (e.g adding headers) you can do it in the JS_REST function.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants