Opened 9 months ago
Last modified 7 months ago
#3616 new bug
HTTP Connect should use tracker domains instead of IP
| Reported by: | Émile Fugulin | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | needs verified |
| Component: | libtorrent | Version: | 2.1.0 |
| Keywords: | Cc: |
Description
Hi!
I believe the current implementation for the HTTP proxy for HTTPS trackers could be improved.
Currently the client sends the following connect:
`
CONNECT <TRACKER IP>:<PORT> HTTP/1.0
`
It should instead use the tracker domain as specified in the RFC 9110 (https://www.rfc-editor.org/rfc/rfc9110#CONNECT) and let the proxy do the DNS resolution and choose the IP.
This is the behaviour of browsers notably because it allows users to have reverse proxies that intercept the TLS traffic if they need it. With only the IP, it's impossible for the proxy to validate the remote server TLS certificate.
Thanks
Note:
See TracTickets
for help on using tickets.
This is something that is being handled by
libtorrent.i would suggest to go and open an issue at their repository: https://github.com/arvidn/libtorrent/issues