Skip to content
This repository has been archived by the owner on Sep 16, 2019. It is now read-only.

Problem With CORS #62

Closed
colomboipl opened this issue Aug 30, 2016 · 5 comments · Fixed by alerta/alerta#248
Closed

Problem With CORS #62

colomboipl opened this issue Aug 30, 2016 · 5 comments · Fixed by alerta/alerta#248

Comments

@colomboipl
Copy link

Cannot login or signup with config.js with basic

Its show the error "Request header field content-type is not allowed by access-control-allow-headers in preflight response.
@satterly
Copy link
Member

What browser and version?

@colomboipl
Copy link
Author

Chrome for centos 6.8 X64bits

This was referenced Sep 3, 2016
Closed
Merged
@satterly
Copy link
Member

satterly commented Sep 6, 2016

See corydolphin/flask-cors#187

@satterly
Copy link
Member

satterly commented Sep 7, 2016

This is fixed by ensuring that Alerta server uses version 2.1.3 of the Flask CORS extension. However, to fix this long term it needs to be fixed in Flask CORS version 3.x so I've raised an issue with them.

@satterly
Copy link
Member

satterly commented Sep 8, 2016

This has been fixed upstream by Flask CORS maintainer (Flask CORS 3.0.2). Alerta server version 4.8.3 which incorporates this fix is now available for download from Pypi.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix versions for flask and flask_cors alerta/alerta
2 participants
@satterly @colomboipl