2025-01-24, 06:44 PM
(This post was last modified: 2025-01-24, 06:49 PM by rkulagow. Edited 1 time in total.)
I just looked at the object in S3, and then also ran the same request with Postman. Both show that AWS is setting the Content-Type to image/jpg
(I understand that you've got a workaround in place, but if the reason for the workaround is that there's no Content-Type, then I think we are sending it on the image requests.)
I re-read what you wrote, and I now realize that you're talking about the header of the downloaded _file_, and not the HTTP transaction.
When I run "file" against the image that we've been discussing, I get:
JPEG image data, JFIF standard 1.01, aspect ratio, density 1x1, segment length 16, baseline, precision 8, 480x720, components 3
So this particular image does seem to have a valid JPEG header?
Anyway, if this is all a moot point, then please let me know. If there's additional troubleshooting that you'd like to perform, then please let me know that too.
(I understand that you've got a workaround in place, but if the reason for the workaround is that there's no Content-Type, then I think we are sending it on the image requests.)
I re-read what you wrote, and I now realize that you're talking about the header of the downloaded _file_, and not the HTTP transaction.
When I run "file" against the image that we've been discussing, I get:
JPEG image data, JFIF standard 1.01, aspect ratio, density 1x1, segment length 16, baseline, precision 8, 480x720, components 3
So this particular image does seem to have a valid JPEG header?
Anyway, if this is all a moot point, then please let me know. If there's additional troubleshooting that you'd like to perform, then please let me know that too.