2025 sparked some incredible conversations across our community 👩💻. Discover the highlights and see what’s ahead in 2026.
Forum Discussion
Video URLs return 403 error
Recently, video links which we get from Dropbox (iOS/Android) Chooser return either a 403 error, or they return 200 but never load.
We are using link type: DbxChooser.ResultType.DIRECT_LINK / D...
Greg-DB
Dropbox Community Moderator
Dropbox Community ModeratorUpdate: in order to temporarily accommodate clients that don’t properly support automatically handling “Transfer-Encoding: chunked”, we’re temporarily rolling back this change, so that these links will no longer use “Transfer-Encoding: chunked” and will instead return “Content-Length” on HTTP/1.1. We will begin rolling that out starting around 2/17. That will be in place until around 3/1. At that point, we will begin using “Transfer-Encoding: chunked” and no longer returning “Content-Length” on HTTP/1.1 again.
Going forward, please ensure that your clients are able to automatically handle both chunked encoding and non-chunked encoding automatically.
Greg-DBDropbox Community Moderator
Dropbox Community ModeratorUpdate: the team has been able to complete some further updates to our infrastructure to be able to support the previous non-chunked behavior going forward indefinitely. That means that we plan to continue returning Content-Length (and not 'Transfer-Encoding: chunked') in the future and will not be reverting this as previously planned. (Regardless, for HTTP compatibility in general, we still recommend you make sure your HTTP clients support both types.) Hope this helps!
Thank you for the update.
Are the changes you discussed already deployed?
I tested now and there is still an error when accessing the files.
- Greg-DB
ephraimt Yes, the current configuration is what we expect to serve going forward. That is, we are returning Content-Length on both HTTP/2 and HTTP/1.1 for these links, like we did originally. If this is currently not working for you, can you share the details of the current error you're seeing? Also, did this start and/or stop working again for you over the last month since your previous message?
It still does not work. Same error as before.
As far as I can tell, it has not worked since the original change.
- Greg-DB
I'm not aware of any remaining issues with how we're serving these on our side. Can you elaborate on what specifically isn't behaving as expected currently? Thanks in advance!
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
