MIME type / Content Type mismatch for realtime uploads

When uploading certain filetypes, i’m getting a mismatch between what the mimetypes.guess_type() returns and what signed header expects for the .

For example, wav files report audio/x-wav and .ogg files report audio/ogg i figured out that the frame.io server is expecting audio/wav and that i had to use application/octet-stream instead of audio/ogg

Is there a list of supported content types, or an easier way for me to determine them on my own?

Hi @hc-evan real-time uploads are a C2C only feature currently, we do not support it for the V4 API at this time. It is on the roadmap for later this year though, no timelines available just yet.

AFAIK mime types are not required for local or remote uploads via the V4 API. The response will tell you what the mime type is though

1 Like

ah ok. I was trying to determine the Content-Type header for the S3 put command from a mimetype call, i see that’s not necessary now!! Thanks

if you need it for the S3 PUT command, the mime type will be returned in the response when you have a successful upload call. It’s called media_type in the JSON response.

1 Like

Thanks @CharlieAnderson Working well now will all filetypes :slight_smile:

1 Like