[Cyberduck-trac] [Cyberduck] #8733: Should not try to resolve address when connecting through HTTP proxy

Cyberduck trac at trac.cyberduck.io
Tue Apr 14 13:57:30 UTC 2015

#8733: Should not try to resolve address when connecting through HTTP proxy
 Reporter:  brian.w.walker@…  |         Owner:  dkocher
     Type:  defect            |        Status:  reopened
 Priority:  high              |     Milestone:  4.7
Component:  s3                |       Version:  4.6.5
 Severity:  major             |    Resolution:
 Keywords:                    |  Architecture:  Intel
 Platform:  Windows 7         |

Comment (by dkocher):

 > We are connecting to an S3 compatible storage bucket on Verizon. We are
 reaching to the internet through our Proxy and our Proxy does the DNS
 resolution  on traffic going out. I think what is happening is that
 Cyberduck is doing DNS lookups via the DNS servers set on the system
 (Internal) and not allowing the Proxy to provide the lookup. So when
 Cyberduck does the DNS request for storage-iad3a.cloud.verizon.com and
 uses the internal servers, it is not able to resolve. We don’t allow
 internal DNS servers to resolve external addresses. ~~What we need is
 Cyberduck to get the DNS lookup form the Proxy on Port 80.~~

 When connecting through the HTTP proxy the target hostname `storage-
 iad3a.cloud.verizon.com` should just be passed in the `CONNECT` header and
 not be resolved. The hostname will be resolved by the proxy and Cyberduck
 does no DNS lookup for the target server at all but only for the proxy.

Ticket URL: <https://trac.cyberduck.io/ticket/8733#comment:5>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows

More information about the Cyberduck-trac mailing list