Provide subdomains of s3auth.com

[jwal]

Is this the best place to leave feature requests?

S3 bucket names are global anyway. I suggest that every registered bucket is given a default subdomain of {bucket}.buckets.s3auth.com. For many use cases it doesn't actually matter what the domain is as long as it provides basic auth over HTTPS access to the bucket.

Using the correct AWS key: Anyone can upload an AWS key for a bucket and configure their own settings. The winner - the person who has their settings applied to the {bucket}.buckets.s3auth.com subdomain - is the first person who uploads the key that allows the .htaccess file to be fetched from the bucket.

Please also register a wildcard HTTPS certificate for *.buckets.s3auth.com so that we can request our bucket content over HTTPS without any further configuration.

[davvd]

@yegor256 please pay attention to this issue

[yegor256]

@jwal thanks for the feature request, sorry it took so long to review it. I see one problem here - the name of a bucket may be very long and contain symbols not suitable for a CNAME... Maybe we can generate a random name for each bucket... What do you think?

[jwal]

Amazon's documentation clearly favors DNS-compatible bucket names and only those that are a single name (no dotted parts) are supported for HTTPS. These same restrictions seem to make sense for s3auth.com subdomains as well. You can pick your own bucket name so if you want to use this new feature you can pick one that works.

You only need to provide access through *.buckets.s3auth.com to buckets with a compatible DNS name without dots.

[yegor256]

@jwal I'm sorry this bug is still not fixed. We didn't have enough funds/time to work on the project. However, recently we received some donations from our grateful users and will continue to fix issues and introduce new features. Would be great if you can also donate -- to help us move forward faster. Here is the link: https://www.0crat.com/contrib/C3RP1J1CH