-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
RxServer cors settings seem to only apply to OPTIONS when using ExpressAdapter #6523
Comments
snimmagadda1
changed the title
RxServer cors settings seem to only apply to OPTIONS requests when using ExpressAdapter
RxServer cors settings seem to only apply to OPTIONS when using ExpressAdapter
Nov 2, 2024
fwiw for my testing, I fixed this by forking the server and changing to |
Hi @snimmagadda1 you fix looks good. Please make a PR with your fix. Also make sure to include a test case. |
sure here's a quick one.. pubkey/rxdb-server#160 |
Thank you, merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've been fiddling with RxServer in node, trying to replicate data from an angular app, and chose the
rxdb-server
package + ExpressAdapter for a QuickStart. I've verified the rest/replication endpoints working via CURL 👍 ; however, I'm noticing that when trying to make requests from my client (localhost:4200) the CORS settings seem to only be set on the OPTIONS responses:Looking at the
RxServerAdapterExpress
class, it seemssetCors
is indeed only setting OPTIONS. Is this intended? The docs here are a bit ambiguous on this point:My server setup:
The text was updated successfully, but these errors were encountered: