cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Share your feedback on the Document Scanning Experience in the Dropbox App right here.

English

With the Dropbox Community you can connect with other users like you, get answers to your questions and discover how to work smarter with Dropbox.

De L.1's Posts

@Здравко Interesting, I don't have any CORS issues with ?raw=1 urls. I tested JPG, MP4, MP3 and PDF file formats embedded directly into a page using iFrame inChrome, Edge and FireFox. Perhaps you ha... See more...
@Здравко Interesting, I don't have any CORS issues with ?raw=1 urls. I tested JPG, MP4, MP3 and PDF file formats embedded directly into a page using iFrame inChrome, Edge and FireFox. Perhaps you have a different use case?
My www.dropbox.com/scl/fi/....?raw=1 urls seem to be working again for a few minutes now. Both images and PDF files. Did Dropbox reverse the change?
@rylincoln That isn't something I can reproduce. Requesting the links returned by /get_temporary_link itself will just give me the correct Content-Type, a 200 HTTP response code and it will download ... See more...
@rylincoln That isn't something I can reproduce. Requesting the links returned by /get_temporary_link itself will just give me the correct Content-Type, a 200 HTTP response code and it will download without problems.   (edit) Ah, I see Greg already responded to this...
When downloading a specific part of a file using the link received via a /get_temporary_link call and the HTTP header Range: bytes=..., the content-type application/grpc is sent instead of the actual... See more...
When downloading a specific part of a file using the link received via a /get_temporary_link call and the HTTP header Range: bytes=..., the content-type application/grpc is sent instead of the actual content-type of the file.   Request Headers:   GET https://uc383828c22b...3d5ecbc28.dl.dropboxusercontent.com/cd/0/get/B61A....17HuE3Lr3UI4EEpPY/file range:bytes=0-   Expected Response Headers:   HTTP/1.1 206 Partial Content --- accept-ranges:bytes Content-Length:26397831 Content-Range:bytes 0-26397830/26397831 content-type:video/mp4     Actual Response Headers:   HTTP/1.1 206 Partial Content --- accept-ranges:bytes Content-Length:26397831 Content-Range:bytes 0-26397830/26397831 content-type:application/grpc     So in this example (actually downloading the full file, but with the Range header), the video file is downloaded with a content-type of application/grpc rather than video/mp4.   This causes problems when (for example) you want to display a video file in an HTML 5 player using the link received from the /get_temporary_link call.  The HTML 5 player buffers the video file and loads the data in chunks. However, due to the incorrect content type, the browser will not accept the data as video content and will not be able to play it. I've just noticed this problem, and I didn't have any problems with it before. So I think this problem has been introduced recently?
Thanks for looking into this, Greg!    Is this perhaps related to the issue discussed on https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Search-shared-folder-suddenly-doesn-t-work/td-p... See more...
Thanks for looking into this, Greg!    Is this perhaps related to the issue discussed on https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Search-shared-folder-suddenly-doesn-t-work/td-p/655510? I started getting reports of this issue a few days ago, so it may be a bug that has been introduced recently.
Hi there!   I am encountering a peculiar issue with the /2/files/search_v2 call in combination with team namespace ids, and I am not sure if this is a bug or the expected behaviour of the API.   ... See more...
Hi there!   I am encountering a peculiar issue with the /2/files/search_v2 call in combination with team namespace ids, and I am not sure if this is a bug or the expected behaviour of the API.   Consider the following team space configuration:     /Team Dropbox (1) /Team Dropbox/Sarah (2) /Team Dropbox/Sarah/Documents /Team Dropbox/Sarah/Documents/Example.doc /Team Dropbox/John (3)   When I make a /2/files/list_folder call using {"path":"/Documents"} with the Sarah account, I get the contents of the /Documents folder, including the file Example.doc. This is all perfectly fine. However, if I also make a call to /2/files/search_v2 using {"query":"Example","options":{"filename_only":true,"path":"/Documents"}} with the Sarah account, I get no results.   After some testing I noticed that the /2/files/list_folder call implicitly uses the home folder of Sarah (home_namespace_id: 2) to list the content. However, the /2/files/search_v2 API call uses the root folder (root_namespace_id: 1). So the search call won't return any results in this case because the /Documents path provided isn't correct.   To resolve this, I can use {"query":"Example","options":{"filename_only":true,"path":"/Sarah/Documents"}} where I add the Sarah home folder in the path. Or I can add the header Dropbox-API-Path-Root: {".tag":"namespace_id","namespace_id":"2"} to the original call. When I do this, the file Example.doc is returned in the search results.   Why are the /files/list_folder and /files/search_v2 calls using a different root/home location? Or is it a bug and should the home_namespace_id (2) also be used implicitly for the /files/search_v2 call, as with the /files/list_folder call? Or am I missing something here? 
OAuth 2 refresh tokens will not expire by themselves. See @Greg-DB answer in this topic. Perhaps a good idea to mention this clearly in the documentation.
Thanks for your quick reply!   I understand that there are no plans yet to disable the old tokens, but I assume that this will happen at some point. But it is good to know that I don't need to forc... See more...
Thanks for your quick reply!   I understand that there are no plans yet to disable the old tokens, but I assume that this will happen at some point. But it is good to know that I don't need to force the users at this moment.  However, as the short-lived tokens with refresh token add an additional level of security, I will have to migrate anyway (at least for new authorizations).    
Hi there,   I want to switch from the depricated long-lived tokens to short-lived access tokens for an application that uses offline access. The old token flow didn't have a refresh token generated... See more...
Hi there,   I want to switch from the depricated long-lived tokens to short-lived access tokens for an application that uses offline access. The old token flow didn't have a refresh token generated. Is it possible to get an refresh token for those old tokens (once) so I can migrate the application to the new short-lived tokens with refresh token without requiring all users to re-authorize?   Thanks!
The 413 error isn't longer thrown so it seems that this issue has been solved. Thanks!
Hi!   I am uploading files (smaller than 150MB) via the temporarily upload links generated via the /get_temporary_upload_link call. This all worked fine, but since a few days the POST upload call... See more...
Hi!   I am uploading files (smaller than 150MB) via the temporarily upload links generated via the /get_temporary_upload_link call. This all worked fine, but since a few days the POST upload call to the generated upload link (e.g. https://dl.dropboxusercontent.com/apitul/1/bNi....)  is terminated with a 413 Payload Too Large error for files larger than a certain limit.   This test-file-5MB works fine but this larger test-file-10MB isn't working.   Is this a known bug or am I missing something?   Cheers!
I just tried it with a device with the latest iOS version (13.4.1) and I am now seeing the same prompt as well. For some reason that wasn't the case when I initially tested this. It turns out that Ap... See more...
I just tried it with a device with the latest iOS version (13.4.1) and I am now seeing the same prompt as well. For some reason that wasn't the case when I initially tested this. It turns out that Apple has finally added the download functionality in mobile Safari as of iOS 13, so it no longer only offers the streaming solution. Good news!   That means that the issue basically remains if you are running iOS 12.x or lower and when you press 'View' instead of download as of version 13. Is there still any chance to still solve that?
Yes, replacing it with '?raw=1' does prevent this issue from happening.   However, I can't change the URL as the use case is that the file should actually be downloaded which it does in all other b... See more...
Yes, replacing it with '?raw=1' does prevent this issue from happening.   However, I can't change the URL as the use case is that the file should actually be downloaded which it does in all other browsers. Unfortunately, iOS Safari will just start streaming the file (by design) which doesn't work with the '?dl=1' parameter.
Hello Dropboxers,   I suddently encounter problems loading media files via a shared link with the ?dl=1 parameter in (at least) the iOS Safari browser.   The following sharing links work fine... See more...
Hello Dropboxers,   I suddently encounter problems loading media files via a shared link with the ?dl=1 parameter in (at least) the iOS Safari browser.   The following sharing links work fine in most browsers, but when I open it in Safari on an iPhone (iOS 12, iOS13), the video isn't loaded and the following error is thrown:   Blocked script execution in 'https://uc370026e834b1ed1889e14a6d89.dl.dropboxusercontent.com/cd/0/get/A1h…01TRE_tte6eGw55OtWcN_gmA6Ca7SCiBItL1b11zEoC1auqe7sUaLUkBTcCX-VQ/file?dl=1#' because the document's frame is sandboxed and the 'allow-scripts' permission is not set.   https://www.dropbox.com/s/c0al0jhjj6hy3a2/Oceanic%20Dawn.mp3?dl=1 https://www.dropbox.com/s/25rn13lnfvtwnky/Avengers%20-%20Endgame%20-%20Trailer.mp4?dl=1   Is this a known bug?   - Floris 
When do you expect that this is solved? Is this a matter of hours/days/weeks?
Hi! I have an issue with shared links with specific characters in the filename when combined with ?dl or ?raw parameter. When I replace the filename part with the ID of the file, the shared link doe... See more...
Hi! I have an issue with shared links with specific characters in the filename when combined with ?dl or ?raw parameter. When I replace the filename part with the ID of the file, the shared link does work (but that isn't the url returned by the API) -------- Example  File Constitucion.pdf (without ó) (Does work) https://www.dropbox.com/s/6ooz5iat88eat9t/Constitucion.pdf?raw=1 File Constitución.pdf (contains a "ó") (Does work) https://www.dropbox.com/s/y2f68dzf8vje3uv/Constituci%C3%B3n.pdf (Link returned by API) (Doesn't work -> redirected to dropbox.com) https://www.dropbox.com/s/y2f68dzf8vje3uv/Constituci%C3%B3n.pdf?raw=1 https://www.dropbox.com/s/y2f68dzf8vje3uv/Constitución.pdf?raw=1 (Does work) https://www.dropbox.com/s/y2f68dzf8vje3uv/id:4tUAwPcrBX0AAAAAAAAzhQ?raw=1 ------- Is this a bug or is there a specific reason for this behavior? And would it be possible to get the shared url with file ID in return of the /get_shared_link_file call to prevent this from happening? I appreciate if anyone can help me out with this issue. Cheers!
I forgot to ask... could you let me know what the current file size limit is so I can set that in my application?
Thanks! Could you add the decision of the team about this feature request in this topic or is there a specific place where I can follow this feature request?
Thanks for your quick reply, Greg! It is indeed disappointing that this link has a file size limit as I basically need the upload possibility without access token for my application. Ofcourse, uploa... See more...
Thanks for your quick reply, Greg! It is indeed disappointing that this link has a file size limit as I basically need the upload possibility without access token for my application. Ofcourse, uploading via the server is possible but that doesn't really make sense for large files as it will take (~)twice as long to upload the files to Dropbox. I would really appreciate it if Dropbox can support uploading of large files without access token for the upload session itself. Is there a specific reason why you think that this cannot be implemented? The other major APIs like the ones for Google One, OneDrive/Sharepoint and Box do support direct uploads where the initial upload link is obtained in the same way as the get_temporary_upload_link' call.    
Hi! I am uploading files via the temporarily upload links generated via the /get_temporary_upload_link call. This all works fine, but the POST upload call to the generated upload link (e.g. https://... See more...
Hi! I am uploading files via the temporarily upload links generated via the /get_temporary_upload_link call. This all works fine, but the POST upload call to the generated upload link (e.g. https://dl.dropboxusercontent.com/apitul/1/bNi....)  is terminated for files larger than a certain limit.   > POST /apitul/1/bNi.... HTTP/1.1 Host: dl.dropboxusercontent.com Accept: */* Content-Length: 536871142 Expect: 100-continue Content-Type: multipart/form-data; boundary=------------------------b315544e35df5ae3 < HTTP/1.1 413 Request Entity Too Large < Server: nginx < Date: Tue, 12 Mar 2019 10:10:15 GMT < Content-Type: text/html < Content-Length: 25658 < Connection: close < ETag: "5c816ae0-643a" < X-Dropbox-Request-Id: 9600532cf40be9d1ae39f8cdd6182848 < X-Robots-Tag: noindex, nofollow, noimageindex < Strict-Transport-Security: max-age=15552000; includeSubDomains < * Closing connection 0   This test-file-200MB works fine but this larger test-file-512MB isn't working. The receiving Dropbox account has enough space available to store the large file. Are there any uploads limits? If there are limits, is there another way to upload files to upload large files via the API without the need of an authorization token? I appreciate if anyone can help me out with this issue. Cheers!