Ensure the private storage class always ignores the optional Boto
setting AWS_S3_CUSTOM_DOMAIN.
Without this hack, when that setting is applied it affects all
storage classes and causes them to generate URLs to S3 objects with
the given domain and without any request signing, producing invalid
URLs for private objects.
Ensure the private storage class always ignores the optional Boto setting
AWS_S3_CUSTOM_DOMAIN
.Without this hack, when that setting is applied it affects all storage classes and causes them to generate URLs to S3 objects with the given domain and without any request signing, producing invalid URLs for private objects.
See related commit for RFDS in amongst the long issue #193: https://github.com/ixc/rfds/commit/a14b0748