-
Notifications
You must be signed in to change notification settings - Fork 154
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
Custom header test failing #116
Comments
You can only repro this by NOT using a proxy, btw. |
A dumb solution that I can confirm works is to just add |
I don't see a good way to fix this, and corser doesn't seem to be recently maintained. Maybe switch to https://github.com/expressjs/cors instead? |
Easiest way to repro:
Does not send back
|
An alternative lib is ok with me it that's the only fix. The main thing would be integrating it with the config again, I imagine (but the current |
This bug can still be repro'd, although for whatever reason it's no longer the case that the PouchDB test suite is failing. |
In the PouchDB test suite, the "custom header" test is failing.
I would like to just whitelist all
X-*
headers, since this is apparently the correct CORS behavior (CouchDB and our proxy both do that), but unfortunately it seems to be an open unresolved issue in Corser: agrueneberg/Corser#2The text was updated successfully, but these errors were encountered: