Proxy '/socket.io' to socket server #1418
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.
Description
Rework how the communication with SocketIO is done. Instead of talking directly with the SocketIO server, proxy the
/socket.io
path to the SocketIO domain.Changes/Tasks
/socket-io
to the SocketIO server__getMessagePort
endpoint in the webpack-dev-serverMotivation and Context
Following the steps outlined in the documentation to enable HTTPS for local development, Safari fails to request data from the SocketIO domain (http://localhost:4000), has it isn't served over HTTPS. Chrome has no issue with this.
Safari logs the following error in the console, originating from
polling-xhr.js
:I have tried to run the SocketIO server on an HTTPS server, without any luck.
Types of changes
Checklist: