-
-
Notifications
You must be signed in to change notification settings - Fork 27k
Another useful case for https in development #8363
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.
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
base: main
Are you sure you want to change the base?
Conversation
It is relevant to note that https in development is important for wss connection speeds. I spent a couple days debugging and this was the solution for slow wss connections.
Hi jaime-ez! Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file.In order for us to review and merge your code, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks! |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
@@ -8,6 +8,8 @@ sidebar_label: HTTPS in Development | |||
|
|||
You may require the dev server to serve pages over HTTPS. One particular case where this could be useful is when using [the "proxy" feature](proxying-api-requests-in-development.md) to proxy requests to an API server when that API server is itself serving HTTPS. | |||
|
|||
Another case is when connecting with secure websockets `wss` to a backend. Doing so from a non HTTPS page may slow down considerably the requests and consequently the development process. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another case is when connecting with secure websockets `wss` to a backend. Doing so from a non HTTPS page may slow down considerably the requests and consequently the development process. | |
Another case is when connecting with secure websockets (aka `wss` - WebSocket Secure) to a backend. Doing so from a non-HTTPS page may slow down requests considerably, slowing down the whole development process. |
Just rephrased this to make it a little clearer!
@jaime-ez Would it be possible to provide a source, for further information about the issue? 🙂 |
It is relevant to note that https in development is important for wss connection speeds. I spent a couple days debugging and this was the solution for slow wss connections.