So, my colleague (wonder95) and I have been dealing with performance issues related to example.com/s3/X urls triggering s3 image style create derivative, etc..
The later versions of s3fs allow control over redirecting vs delivering them. One thing I notice with both options is varnish was not caching these items. Not caching the delivered or the redirection (not sure if our provider does any caching of 302, though the option of even allowing a 301 would help too)
Is it possible to add control over the header / caching options within the interface? Just a thought, ideally we would want to serve up CDN urls only, but you are surely aware of the s3fs / insert module combination regarding that.
Closed: won't fix
2.0
User interface
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.
There was previously an open issue for the D8+ branches at ✨ Add setting to return 301 or 302 response for images Active that was closed as won't-fix due to technical limitations.
We have also improved cache clearing to reduce the times that style paths are generated in code.