Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Error 400 when trying to download a file
Hello, I'm using Dropbox for OTA. It worked for long time up until couple of weeks ago. Now, connection is established, folder list is downloaded, but when trying to download a file, I'm receivi...
Here is a capture of the request when redirected to AWS (API Gateway service). It looks perfectly correct:
(bdc789db-0418-470d-8cd0-c875d80b44b3) Method request headers: {Authorization=*******************************************************************************************************************************************CLnyJw, X-Forwarded-Proto=https, X-Forwarded-For=2.53.174.13, Host=d13k3bi9ke.execute-api.us-east-1.amazonaws.com, X-Forwarded-Port=443, X-Amzn-Trace-Id=Root=1-65e41272-37ecaf0e7538265a0082a13f, Content-Type=application/json}
(bdc789db-0418-470d-8cd0-c875d80b44b3) Method request body before transformations: {
"path": "/ota_bundle_office/20240221072512_CC3220SF.tar"
}
Adding the fact that the request is perfectly decoded by other servers (I tried AWS and httpdump.app) to the fact that it worked perfectly with Dropbox.com up until couple of weeks ago, might show that a recent change that you made in your server is the root cause for this issue. I do not think that this is a format issue. Please advise. Thanks
Greg-DB
Dropbox Community Moderator
Dropbox Community ModeratorThat doesn't seem to be the raw request, and regardless it's not the request to the Dropbox servers directly, so unfortunately we can't use that to debug this.
Whatever the issue is, we'll need to be able to reproduce the issue to confirm what is going wrong and how to fix it. I replicated the request you shared earlier, but that did not reproduce the issue, so it does not seem that that is a correct representation of the request being made. It's important to make sure we're investigating the exact right requests; sometimes substituting in different servers can be misleading as different servers may support different protocols/versions/features. For example, different servers may support different versions of the HTTP protocol, like how the api.dropboxapi.com servers support both HTTP/1.1 and HTTP/2, and will prefer HTTP/2 when possible.
Have you been able to reproduce the issue outside of that particular embedded system? Please let us know how to reproduce the issue, e.g., using curl, so we can investigate.
Another thing to note is to make sure that the client is sending the exact full amount of data as specified in the 'Content-Length' request header. If the client doesn't send that amount of data, the server can respond with that error.
As I wrote above, this is an embedded system and I'm using a library of the chip vendor, Texas Instrument (TI). Hence, I do not have access to exact format of the HTTP request.
I can only direct the request to another server (as I did with AWS and httpdump.app) or ask you for a log from your server that shows the mismatch, which then I can share with TI and ask them to fix.
- Greg-DB
Dropbox doesn't offer request logs like that, so unfortunately I can't provide a copy of the request that the client made. That kind of inspection would need to be done client-side.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
