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

streamer websocket handshake error: Header HTTP_UPGRADE is not defined #2296

Closed
nickstenning opened this Issue Jun 7, 2015 · 5 comments

Comments

Projects
None yet
2 participants
@nickstenning
Copy link
Contributor

nickstenning commented Jun 7, 2015

https://app.getsentry.com/hypothesis/prod/group/61157091/

I'm not entirely sure what this error is at a glance, but it seems to be non-websocket client connections to the websocket. Needs investigation to determine if worrisome, and if not we should silence the error.

@tilgovi

This comment has been minimized.

Copy link
Contributor

tilgovi commented Sep 9, 2015

Not seeing this anymore.

@tilgovi tilgovi closed this Sep 9, 2015

@nickstenning nickstenning reopened this Sep 16, 2015

@nickstenning

This comment has been minimized.

Copy link
Contributor Author

nickstenning commented Sep 16, 2015

All over the logs. Reopened.

@nickstenning

This comment has been minimized.

Copy link
Contributor Author

nickstenning commented Sep 16, 2015

Raising to P2 because the sheer volume of these is worrying.

@tilgovi tilgovi closed this in a0244c2 Sep 18, 2015

tilgovi added a commit that referenced this issue Sep 18, 2015

@nickstenning

This comment has been minimized.

Copy link
Contributor Author

nickstenning commented Sep 18, 2015

Any insight into why we're getting so many hits at that endpoint? I ask because I don't see that this changes anything other than removing the log line...

@tilgovi

This comment has been minimized.

Copy link
Contributor

tilgovi commented Sep 18, 2015

Nope. :-(

On Fri, Sep 18, 2015, 00:58 Nick Stenning notifications@github.com wrote:

Any insight into why we're getting so many hits at that endpoint? I ask
because I don't see that this changes anything other than removing the log
line...


Reply to this email directly or view it on GitHub
#2296 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.