-
Notifications
You must be signed in to change notification settings - Fork 147
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
docs: update anonymizeProxy
docs
#536
Conversation
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.
Thanks Jirka
@@ -368,7 +368,7 @@ The package also provides several utility functions. | |||
|
|||
Parses and validates a HTTP proxy URL. If the proxy requires authentication, | |||
then the function starts an open local proxy server that forwards to the proxy. | |||
The port is chosen randomly. | |||
The port (on which the local proxy server will start) can be set via the `port` property of the first argument, if not provided, it will be chosen randomly. |
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.
What happens if you reuse the same port - the old proxy is replaced?
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.
No, if the old local proxy server is running, you'd get e.g. Error: listen EADDRINUSE: address already in use
, because the port is already in use. I believe this is a standard error, it's very similar to cases like trying to start local web servers on the same port.
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.
I see, thanks
No description provided.