Dropbox link as MediaConvert HTTP input

0

In the last week of January 2022, Dropbox changed the http response headers of "Direct Links". Direct links are temporary public URLs that return a Dropbox file.

When calling the link with HTTP/1.1, Dropbox now returns the "Transfer-Encoding: chunked" header and no longer returns a "Content-Length" header in the response.

As a result, when these links are used as an HTTP-type input for a MediaConvert job, the job fails with error 3450 HTTP Server Error: You specified an HTTP URL for an input file, but the HTTP server returned an error or failed.

These links work fine when called them from a browser or Postman, so the problem seems to be in how MediaConvert handles the response.

Has anyone else experienced this, or have any suggestions to work around?

asked 2 years ago72 views
No Answers

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions