Skip to content
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

Why the sanic websocket close from the client got an error? #708

Closed
ihjmh opened this issue May 11, 2017 · 3 comments
Closed

Why the sanic websocket close from the client got an error? #708

ihjmh opened this issue May 11, 2017 · 3 comments

Comments

@ihjmh
Copy link

ihjmh commented May 11, 2017

After clinet close the websocket ,I got errors like this:

[ERROR]: Exception occured in one of response middleware handlers
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/sanic-0.5.4-py3.5.egg/sanic/app.py", line 495, in handle_request
    response)
  File "/usr/local/lib/python3.5/dist-packages/sanic-0.5.4-py3.5.egg/sanic/app.py", line 621, in _run_response_middleware
    _response = await _response
  File "/home/oeasy/.local/lib/python3.5/site-packages/sanic_cors/extension.py", line 237, in cors_response_middleware
    elif resp.headers.get(ACL_ORIGIN):
AttributeError: 'NoneType' object has no attribute 'headers'

In fact,I wanna a normal notification that I can use, the source codes are from the sanic example
Anyone can help me?Thanks very much !

@seemethere
Copy link
Member

Looks like an issue with the the sanic_cors package not necessarily core sanic

@qwexvf
Copy link

qwexvf commented May 14, 2017

Already reported but.....
ashleysommer/sanic-cors#2

sad .,

@seemethere
Copy link
Member

Looks like it got cleared up on the extension side, closing for now. Will re-open if necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants