Missing CORS headers when write actions are rejected
- Dominant language
- Python
- Stars
- 26
- Forks
- 28
- Avg merge
- 4h
- Merged PRs (30d)
- 9
Description
See also https://github.com/c2corg/v6_ui/pull/1989#issuecomment-362035223
Tested in prod, demo and in a personal instance:
* if a write action is accepted, nothing special is reported on the UI side in browsers' dev consoles
* on the other hand, if the write action is rejected (blocked or rate limited user, 500 error?), the UI error processing is not performed as expected (https://github.com/c2corg/v6_ui/pull/1989) and CORS errors are reported in the browsers' dev consoles:
It seems CORS headers are not returned when an exception is raised while processing the request.
* failed request (user is blocked):
* successful request:
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.