Results 340 comments of Dan Gould

Based on some examples [using 8080 in this codebase], I have a feeling it was just a mistake carried over in testing. The RFC that defines HTTP and the CONNECT...

Looks like [SOCKS conventionally listens on port 1080 by spec](https://datatracker.ietf.org/doc/html/rfc1928#section-3) actually, so I've adjusted the default behavior to match that too

force pushed to fix clippy lints

In further testing, I discovered that `Url::parse` discards the port if it is assumed to be the default port for the scheme. So, for example passing `Url::parse(&"http://example.com:80")?` to the proxy...

> So what are we saying the behavior for http://example.com:80 should be with regards to the proxy port? ## Current behavior - an `Agent` with `Proxy::new("http://example.com:80")` sends requests to `example.com:8080`...

Yes. I think this is a breaking change for anyone depending on the 8080 default. That's an odd behavior to depend on but I wouldn't say it's impossible.

Thanks for sticking with me and merging this. I think this makes #719 a bit easier so I'll have a revisit to that now

force pushed to fix clippy lints

I'd love to see the latest published. Those changes would help out a ton