When serving files from S3 via SSL there are a variety of scenarios where you end up with invalid certificate errors. For example, if your bucket has one or more dots in the name or you are using a CNAME alias.
Suggestion would be to fallback to the https://s3.amazonaws.com/[bucketname]/[object] format in this situation rather than failing to serve the content.
Patch coming in a sec.
Thanks...
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | storage_api-s3-ssl-1979774-2.patch | 1.17 KB | jtolj |
| #1 | storage_api-s3-ssl-1979774-2.patch | 1.17 KB | jtolj |
Comments
Comment #1
jtolj commentedAnd here is the suggested patch.
Comment #2
jtolj commentedSorry, mistake in the CNAME/SSL logic. Corrected patch attached.
Comment #2.0
jtolj commentedtypo
Comment #3
perignon commentedGood suggestion. I'll see about getting this added. The patch is no longer good because of other changes to the S3 provider that happened in the last few months.
Comment #5
perignon commentedCommited to Dev.
Comment #6
jonhattanFor some reason a $ was lost.
Comment #7
jonhattanForget me. It was already fixed in ff3d5dc8
Comment #8
perignon commentedLOL. No worries!
Comment #10
perignon commented