Hi
S3 has been used on one of our sites properly for sometime. Recently we decided to make 2 changes: use a CNAME instead of the standard Amazon bucket name and also move all pages to SSL. This is when issues started. We also have cloud front running on the S3 bucket.
Steps to re-create,
- Settings: Cname record put in (it's configured on our DNS) and https setting is un-checked on S3FS
- Secure pages module has been configured to send all pages to https
- A new node is created an an image uploaded
- After creation, Drupal display the node but the image is not displayed
- If the image is opened in a new tab, the path points to https://[SITE SERVER ADDRESS]
- File does not appear on the Amazon S3 bucket
Temporary Solution we are using,
- Change the CNAME to the name assigned by Amazon S3
- Open the image in a new tab and change the path to http://[SITE SERVER ADDRESS]
- File is then picked up by cloud front cdn and starts to display
- The file also starts to appear in the Amazon S3 bucket
Is this supposed to be normal behaviour or do you think something has been configured incorrectly?
Active
2.3
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Drupal 7 end-of-life triage:
Drupal 7 reached end of life on January 5th.
The 7.x branches of S3FS do not have any additional planned releases.
The requests in this issue do not appear to exist in the 8.x-3.x and newer branches.