Does not check the Upgrade response Sec-WebSocket-Accept
#334
Labels
Comments
|
Would you look at that. Can't believe I missed that. Thanks for the link. Certainly something that should be addressed. Thanks! |
sahara108
added a commit
to senagbe/Starscream
that referenced
this issue
Jul 18, 2017
* 'master' of github.com:daltoniam/Starscream: (22 commits) updated podspec the joys of getting all the package manager to play nice Removed Else Clause that would sometimes give a wrong error message updated changelog updated pod spec for compression changes SecTrust object now is conditionally unwrapped spm fix spm fix package manager update fixes daltoniam#309, daltoniam#319, daltoniam#334 make WSResponse values public Add Advanced Delegate and Custom HTTP methods Update README with (trite) grammar changes Include zlib as a module, rather than using `@_silgen_name` and redefinition. This is less verbose and less error-prone. Add information about compression support to README. Other changes based on PR feedback. Avoid unnecessary copying. Confirm Autobahn fuzzing test results are comparable with the autobahn library itself. Fix capture memory leaks in Autobahn tester. Fixes to handle different windowsBits and noContextTakeover. Integrate compression classes. Add compression classes and unit tests. ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://github.com/daltoniam/Starscream/blob/master/Source/WebSocket.swift#L581-L583
This should be validated as being equal:
The reason for this is to ensure that the web socket is not behind a caching layer.
see https://tools.ietf.org/html/rfc6455 page 24
The text was updated successfully, but these errors were encountered: