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.

Sign up for GitHub

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

Jump to bottom

WebSockets discovery script #16

Open
bonsaiviking opened this issue Dec 10, 2014 · 3 comments
Open

WebSockets discovery script #16

bonsaiviking opened this issue Dec 10, 2014 · 3 comments
Labels
enhancement have code NSE

Comments

@bonsaiviking
Copy link
Contributor

Submission from @d33tah

https://gist.github.com/d33tah/b902eb4e10c1e2b8e095
@majek majek closed this as completed Dec 10, 2014
@bonsaiviking bonsaiviking reopened this Dec 10, 2014
@bonsaiviking
Copy link
Contributor Author

Can you include a comment as to how you came up with the value for the Sec-WebSocket-Key header? Does this vary from implementation to implementation? How about Sec-WebSocket-Version?

@d33tah
Copy link

d33tah commented Dec 10, 2014

Honestly I can't remember anymore, but I can try to reproduce it. I suppose that I copied it from some tramisssion generated by some other software, like Firefox or socat when I tested against echo.websocket.org.

@d33tah
Copy link

d33tah commented Dec 27, 2014

I just tried to reproduce it - I visited http:https://www.websocket.org/echo.html using Firefox 34 while sniffing for 174.129.224.73 and got these headers (and a few more).

@jstevensog jstevensog mentioned this issue Apr 11, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement have code NSE
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@majek @d33tah @bonsaiviking