Repository navigation
Support PAC files for proxy configuration #2607
Description
Activity
anonymous commented
Replying to [comment:1 dkocher]:
SOCKS Proxy settings are read from System Preferences and should be used. Have you tried?
I have tried, and the System Preferences for Network settings (SOCKS) are not used.
00c6057 commented
This is still an issue with the latest version (3.8.1) on Snow Leopard (10.6.6). Sorry for the delay in re-opening, but just noticed it. Let me be a bit more specific:
First some assumptions:
- The host "server.domain.com" (SERVER) is a publicly accessible SSH server that also runs DNS services and a WebDAV server.
- SERVER is also configured to resolve multiple subdomains of the form: SUBDOMAIN.domain.com. Clients can make DNS requests over SSH to resolve these subdomains, but the server won't resolve them over the public net.
Steps to reproduce:
- Go to System Preferences->Network, then Advanced, then Proxies, and select Automatic Proxy Configuration. Select a PAC file with contents like:
function FindProxyForURL(url, host) { // SOCKS proxy everything to SUBDOMAIN.domain.com if (isPlainHostName(host)) return "DIRECT"; else if (shExpMatch(url, "http://www.domain.com*")) return "DIRECT"; else if (shExpMatch(url, "http://*.domain.com*")) return "SOCKS localhost:8001"; else return "DIRECT"; }- Open an SSH tunnel using a command like the following from a Terminal window. Note that it accesses a public server URL and maps the local SOCKS port. Also note that the PAC file will also route DNS requests over the tunnel, so SUBDOMAIN.domain.com will not be resolvable on the public DNS.
ssh server.domain.com -D 8001- Now try to configure CyberDuck for a connection to WebDAV (non-SSL) using http://SUBDOMAIN.domain.com/webdav/. The connection will always fail.
- Now you'll see the confusion in Cyberduck. There is no need for a username, password, or port specification. If it really used the system network settings, it would dynamically route all requests over the SSH tunnel via system settings and the PAC file.
- locked as resolved and limited conversation to collaborators
on Nov 26, 2021
I normally connect to WebDAV using an SSH tunnel and SOCKS proxy within the browser. I would like to use Cyberduck instead of the Mac OS X WebDAV client, which uses SOCKS if it's configured in Network Preferences. Note that SOCKS can be specified either as a specific SOCKS proxy server, or by using a PAC file that specifies SOCKS based on its own logic.
Please add support in Cyberduck to connect to a WebDAV server using these parameters:
hostname: subdomain.domain.com
username:
password:
port:
protocol: WebDAV (no SSH)