Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support PAC files for proxy configuration #2607

Closed
cyberduck opened this issue Sep 26, 2008 · 8 comments
Closed

Support PAC files for proxy configuration #2607

cyberduck opened this issue Sep 26, 2008 · 8 comments
Assignees
Milestone

Comments

@cyberduck
Copy link
Collaborator

anonymous created the issue

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)

@cyberduck
Copy link
Collaborator Author

@dkocher commented

SOCKS Proxy settings are read from System Preferences and should be used. Have you tried?

@cyberduck
Copy link
Collaborator Author

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.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I cannot replicate this in version 3.3. Please reopen if this is still an issue for you.

@cyberduck
Copy link
Collaborator Author

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.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

The setting for a PAC file is currently ignored set in the system network settings on Mac OS X.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

PAC configuration is supported for Cyberduck on Windows as of 3072fe1. See #6968.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#8085 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 99a49e3.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants