Bug 251285
| Summary: | [WinCairo] Socks proxy resolves DNS locally instead of server | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Max Schmitt <max> |
| Component: | Platform | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | fujii.hironori |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Windows 10 | ||
Max Schmitt
WebKit Linux and macOS does when setting a socks5 proxy resolve the hostname on the socks server end. This means it sends the hostname to the socks server. The current implementation on Windows when using cURL does instead resolve it locally and just send the IP address to the socks server. This is different to how its done on Linux/macOS, Firefox, and Chromium.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Fujii Hironori
libcurl clearly documents the spec.
https://curl.se/libcurl/c/CURLOPT_PROXY.html
I've never used socks proxies. I don't know how important cURL's "socks5://" behavior.
But, if it's important for someone, WinCairo should keep both "socks5://" and "socks5h://" behaviors.
I think it should be kept as Playwright's logic.
https://github.com/microsoft/playwright/issues/20451
Max Schmitt
Yes I'm totally fine with keeping it like this, since this was easily fixable on Playwright side (to align it).
Filed it more to have an upstream reference which can be linked to for further users who run in it.
Thanks Fujii.