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
Expose Location Header in CORS #189
Labels
Comments
I am working on a fix for this -- putting the comment here because I belatedly realized I don't have permissions to assign myself the ticket. |
coverbeck
added a commit
to coverbeck/cwlviewer
that referenced
this issue
Feb 7, 2018
Also update README.md explaining how to get unit tests running
coverbeck
added a commit
to coverbeck/cwlviewer
that referenced
this issue
Feb 7, 2018
Also update README.md explaining how to get unit tests running
coverbeck
added a commit
to coverbeck/cwlviewer
that referenced
this issue
Feb 7, 2018
Also update README.md explaining how to get unit tests running
coverbeck
added a commit
to coverbeck/cwlviewer
that referenced
this issue
Feb 7, 2018
Also update README.md explaining how to get unit tests running
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Cwlviewer should add
Access-Control-Expose-Headers: Location
.When doing a POST to add a new workflow, if the response status is a 202, the Location header indicates the url to check the queue status. Because the above header is not in the response, the browser cannot see the location of the queue, and thus cannot check the queue status.
This relates to #186 and dockstore/dockstore#1058.
The text was updated successfully, but these errors were encountered: