Prioritise WS for optimal transport #250
Merged
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.
In raising this pull request, I confirm the following (please check boxes):
Description of change
Without these changes, we will always be
pulling
even if there is implementation ofwebsocket
./.well-known/
is allowed RFC5785 (Let's Encrypt).app.listener = io.connect($('meta[name="socket_url"]').attr('content'), { query: 'jwt=' + $('meta[name="jwt"]').attr('content'), + transports: ['websocket', 'polling'] });