Sec-Websocket-origin no longer mandatory in protocol-upgrade headers. #174
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was just messing around with dart language. Dart:io doesn't send Sec-Websocket-Origin header so a dart websocket can't talk to cyclone websocket. I believe this header is no longer mandatory. I'm not sure if "UNKNOWN" is an appropriate value but this seems to fix dart<->cyclone interop.