-
Notifications
You must be signed in to change notification settings - Fork 280
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
Add CORS handling in the proxy #6
Comments
ok, I will look into it. |
I will integrate this library: https://github.com/troygoode/node-cors in redbird for complete CORS support. |
Thank you for your quick answer. I think the most important bit is CORS preflight (at least for http -> https redirect). |
Sorry, I was wrong, I think preflight has nothing to do with http to https redirect. |
+1 |
Hi @manast . Just wanted to know if this issue will be implemented soon ? if any help needed - just say . best regards, |
@eladh I do not have the requirement myself so I do not really know where to start :) You are welcome to help if you want to. |
the readme says there is cors support but there isn't. any updates on this? |
Any progress on this? 👀 Just want to add |
time for a PR 💪 |
Hi,
Thanks for the great work on redbird, we've been using it in production for about 2 weeks, and we're quite happy with it 🍻, especially the HTTPs support is great!
The only problem we had, that is more an annoyance than a bug, is that we had to disable redirect because it is not compatible with CORS, since the 302 headers do not have any CORS information.
Would it be possible to add support for CORS inside redbird? That would be most appreciated (and useful).
Thanks!
The text was updated successfully, but these errors were encountered: