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...

Comments

jtolj’s picture

Status: Active » Needs review
StatusFileSize
new1.17 KB

And here is the suggested patch.

jtolj’s picture

StatusFileSize
new1.17 KB

Sorry, mistake in the CNAME/SSL logic. Corrected patch attached.

jtolj’s picture

Issue summary: View changes

typo

perignon’s picture

Assigned: Unassigned » perignon
Issue summary: View changes

Good 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.

  • Perignon committed 6ab02f6 on 7.x-1.x authored by jtolj
    Issue #1979774 by jtolj: Better S3 SSL support
    
perignon’s picture

Commited to Dev.

jonhattan’s picture

Priority: Normal » Major
StatusFileSize
new488 bytes

For some reason a $ was lost.

jonhattan’s picture

Priority: Major » Normal

Forget me. It was already fixed in ff3d5dc8

perignon’s picture

Status: Needs review » Fixed

LOL. No worries!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

perignon’s picture

Issue tags: +Storage API 7.x-1.7