-
Notifications
You must be signed in to change notification settings - Fork 22
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
Please help! #2
Comments
Hi @qwexvf |
Ok, it looks as if somehow
If you are explicitly setting |
Closing as invalid |
No, I didn't set to None,
Now i got this! |
And on the browser console i got this
any advice ? |
Sorry ignore all of them. i was running the examples which those routes does not exist lol. Nice extension <3 keep it up! Edit:
|
@qwexvf can you make sure you're using the latest version of this module? |
Im going to reopen this issue, I think it has something to do with the extension attempting to modify the headers of an Exception response. |
@r0fls since now im using cors to specific resource i'm not having this issue anymore. |
I believe this issue was created before Websockets were added to Sanic. It is possible that when this issue was opened, the error was originally caused by using the example code on routes which did not exist, and now the same error is seen when Websockets are used with Sanic-CORS. |
This should be fixed by: 6d88deb |
Hi all, sanic version: 0.6.0 |
Thanks for the report. I am aware sanic-cors does not currently work on websocket connections. I can push a patch later today to fix that crash. |
in the case of using websockets Fix other edge cases where `response` might be `None` and don't try to apply CORS to these cases Bump to version 0.6.0.1
@vromanov |
Thanks for the quick support! It works perfectly! |
I still see this issue on the latest version. I'm using a websocket.
|
i got some issue!
Thanks!
The text was updated successfully, but these errors were encountered: