Gallery API - Returned Image Type not matching HTTP-Content header of URL

[ohc-integration]

Hello all,

I'm developing integrations with other third party providers where I can supply a URL and they ingest that information. However, I was told there were errors with the image.

On investigation, the "type" provided by the API (image/jpeg). However, the HTTP Content type is actually binary (application/octet-stream) and the filename is inlined in the content-disposition. I understand this may have been used for file downloads, but this post seems to think this isn't necessary. This seems more like a bug, as really the "type" is provided by the API, so I'm not sure its not set b the content-type.

Would this ask be possible? I've been running into this issue several times. My other option is to download it locally and transfer more data that way, but fixing the HTTP Content Type is preferred.

[tilmonedwards]

I just ran into this today. Thanks to a really vague error message from supabase it took me a few hours to figure out what was going on. I opened a PR for supabase about it here if you want to read the whole saga.

Ultimately it seems like the content type on the `Attachment` is correct, it's just the content type from actually downloading the image file that's sometimes wrong. (Only sometimes! Most of my images worked fine, but a small handful had this `application/octet-stream` behavior.)

[ohc-integration]

@tilmonedwardsIs there a way for us to request a change in behavior on AirTable? You are the first reply, and from the looks of posts, AirTable doesn't seem to monitor this forum at all for bugs.

[tilmonedwards]

@ohc-integration Looks like there's a way to contact Airtable from within the app. https://support.airtable.com/docs/contacting-airtable-support