-
-
Notifications
You must be signed in to change notification settings - Fork 958
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
CORS support #3028
Comments
This is intentional setup, can you please clarify what is your use case for this |
updated description. |
I don't think it's reasonable to set it on whole Weblate, it might be better just on selected endpoints you are using? |
What do you mean by selected endpoints ? |
Selected URLs. Can you please describe what is your use case? Why do you need to do CORS against Weblate? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Reopening based on #6665 and WeblateOrg/docker#1694 |
Thank you for your report; the issue you have reported has just been fixed.
|
Is your feature request related to a problem? Please describe.
I am sending a request for a Weblate, and the response does not have
Access-Control-Allow-Origin
headers, and therefore the browser rejects responses from the server with the errorAccess to XMLHttpRequest at * from origin 'http://localhost' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: Redirect is not allowed for a preflight request
.Can Weblate provide any solution for setting Access-Control-Allow-Origin headers?
Describe the solution you'd like
Currently I am adding a corsheaders library to
settings.py
. But it would be easier in the future to have CORS headers support built-in.Describe alternatives you've considered
No alternatives.
Additional context
No context
The text was updated successfully, but these errors were encountered: