HTTPS otherthan 443 is not connecting
- Dominant language
- JavaScript
- Stars
- 7.9k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
Plese fill the template when you reporting a new issue, thanks!
#### Which platform are you running AnyProxy
Windows
#### The version of the AnyProxy
anyproxy@4.1.0
#### Your expected behavior of AnyProxy
when i try to access https://139.59.86.53:3001/ , should get the response from server as "["unauthorized"]".my server https port is 3001
but its working fine for other https site with port 443.
#### The actual behavior of AnyProxy
but i am getiing the below error message "timedout"
[AnyProxy ERROR][2019-08-09 21:10:37]: Error: connect ETIMEDOUT 139.59.86.53:57925
#### The log of the error
D:\working\pt>node --inspect rec
Debugger listening on ws://127.0.0.1:9229/501b73af-c432-4c8a-9215-00a7ffbaa443
For help see https://nodejs.org/en/docs/inspector
[AnyProxy WARN][2019-08-09 21:09:52]: both "-i(--intercept)" and rule.beforeDealHttpsRequest are specified, the "-i" option will be ignored.
[AnyProxy Log][2019-08-09 21:09:52]: throttle :10000kb/s
[AnyProxy Log][2019-08-09 21:09:52]: Http proxy started on port 8001
[AnyProxy Log][2019-08-09 21:09:52]: web interface started on port 8002
[AnyProxy Log][2019-08-09 21:09:52]: Active rule is: my customized rule for AnyProxy
Debugger attached.
[AnyProxy Log][2019-08-09 21:09:55]: received https CONNECT request 139.59.86.53
[AnyProxy Log][2019-08-09 21:09:55]: will forward to local https server
[AnyProxy Log][2019-08-09 21:09:55]: received https CONNECT request 139.59.86.53
[AnyProxy Log][2019-08-09 21:09:55]: will forward to local https server
[AnyProxy ERROR][2019-08-09 21:10:37]: Error: connect ETIMEDOUT 139.59.86.53:57925
Contributor guide
No contributing guide indexed for this repository
Research direction
Begin with the custom rule and the HTTPS CONNECT forwarding path described in the log, using the Windows setup and AnyProxy 4.1.0 details as the reproduction context. Compare the failing HTTPS endpoint on port 3001 with the working port-443 case and inspect the recorded timeout. Done means the endpoint returns the expected unauthorized response without a timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100