i have a question, anyone faced an issue like havi...
# lucee
g
i have a question, anyone faced an issue like having bucket names like this: s3.myfiles and when serve using the netweok, actually get https error and the file is broken due to certificate, if yes, anyone knows how can i fix that, because the certifcate is valid but amazon s3 seems to be in problem
p
Need more clarity than just that. What errors, stack info etc are you receiving?
a
It's an HTTPS cert error caused by your bucket's name having a period in it. That name appears in the URL, with that period, and the cert AWS uses can't auth it.
g
ok, i am getting net::ERR_FAILED, i am serving it http, in firefox, its loading but not loading in any other browser i am using amazon s3 sdk by ortus
but is there a way i can bypass it, because bucket renaming seems impossible as we have existing data which is already using it
p
Probably should have planned better naming conventions. You may need to rename them all.
Shouldnt be hard, a bulk script
g
what kind of bulk script
it seems the periods solving problem
amazon should really work on this
p
You are not comprehending the issue; the bucket name with a period in it makes the URL appear like a subdomain thus the browser/ssl technology comprehends it as a subdomain but S3's cert fails because it doesnt have a subdomain; your folder is jacking up the url for the browser's processing.
g
oh ok
Thanks for the details
👍🏻 1