The resulting links do support byte ranges though. These modified shared links will return redirects though, so the client will have to follow them. Using the URL parameters dl=1 or raw=1 is the right way to do so. By default, shared links point to a preview page, so you will need to modify them. If a link isn't currently banned though, it can be used to access file content.
An error code of 429 indicates the link is banned for too much traffic. You should check the error code for that. If shared links aren't working, that's one possible cause. If any of the above is the case, is there a way to alter something on the Dropbox side, or using PHP or any other techniques to fetch the link and present it differently?ĭropbox does have bandwidth limits for shared links. NOTE: I tried to set up a snippet, but couldn't get it to work with external libraries. Is that the same thing as the byte-range issue or how do I make sure of that? Another lead told me to "make sure your app can follow redirects". In the example below, is there any way to find out if that is the case? I don't know where to look for the headers. My googling has pointed me in the direction that the issue might be that Dropbox doesn't send byte-ranges, which is said to be necessary for iOS/Safari and even Chrome. I'm using videojs to play videos hosted on Dropbox, but users report that it doesn't work on iPhones (iOS) and for some users the video doesn't play in their browser either half of the times.Īnyone know if Dropbox has any bandwidth/connection limits on this? I'm intending on having top 10 users watching each link so it shouldn't be an issue.Īnyone know if I should use raw=1 or dl=1 at the end of the links for embedded content from Dropbox?
0 kommentar(er)
