Cyberduck Mountain Duck CLI

Changes between Initial Version and Version 1 of Ticket #11416


Ignore:
Timestamp:
Dec 11, 2020 12:17:15 PM (10 months ago)
Author:
dkocher
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #11416 – Description

    initial v1  
    11Hi,
    22
    3 according to the changelog of 7.2.0 and this ticket (https://trac.cyberduck.io/ticket/10956), the possibility to configure path-style for S3 was removed. Later two mechanisms were added to automatically detect when path-style should be used:
     3according to the changelog of 7.2.0 and this ticket (#10956), the possibility to configure path-style for S3 was removed. Later two mechanisms were added to automatically detect when path-style should be used:
    44
    55- Situation 1: When server is an IP address: https://trac.cyberduck.io/changeset/48257
    6 - Situation 2: When A/AAAA record for bucket.hostname.example is answered with `NXDOMAIN`: https://trac.cyberduck.io/changeset/48332
     6- Situation 2: When A/AAAA record for bucket.hostname.example is answered with `NXDOMAIN`: r48332
    77
    88However, there are use-cases when both situations don't apply but path-style might still be required for the connection to work.
     
    1010For me situation 1 will not apply as I have to use a domain name so the SSL certificate can be verified. Situation 2 also does not apply because we're using wildcard DNS records for `*.hostname.example`. In this case Cyberduck checks for a A record of `bucket.hostname.example` which obviously exists but it does not point to the correct system as the S3 system is configured to work with path-style buckets only.
    1111
    12 Other people are having the same issue with wildcard DNS setup (https://trac.cyberduck.io/ticket/10956#comment:10) or with a nameserver of their provider which answers to requests with own IP addresses (https://trac.cyberduck.io/ticket/10888#comment:31, bad practice but it's out there..).
     12Other people are having the same issue with wildcard DNS setup (#10956#comment:10) or with a nameserver of their provider which answers to requests with own IP addresses (#10888#comment:31, bad practice but it's out there..).
    1313
    1414Therefore it would be great to have a config option to disable the automatic detection and specifically set the mode to path-style.