You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
useNamedSocket option is not working properly.
- On windows + nodejs 5.6 it crash nodejs
- On unix it works on most requests but fail on others (ex: all images
on twitter), when creating the internal socket connection.
Both may be due to concurrent connection over the same named pipe but I
don't have enough information to be sure.
This experiment is not yet working and should be removed from master
Copy file name to clipboardExpand all lines: README.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -122,7 +122,6 @@ __Arguments__
122
122
* httpsAgent - The [https.Agent](https://nodejs.org/api/https.html#https_class_https_agent) to use when making https requests. Useful for chaining proxys. (default: internal Agent)
123
123
* forceSNI - force use of [SNI](https://en.wikipedia.org/wiki/Server_Name_Indication) by the client. Allow node-http-mitm-proxy to handle all HTTPS requests with a single internal server.
124
124
* httpsPort - The port or named socket for https server to listen on. _(forceSNI must be enabled)_
125
-
* useNamedSocket - use named socket (i.e. unix socket or named pipe) instead of TCP ports for internal server(s)
0 commit comments