Child Item

503 Errors depending on HTTP client

When using the endpoint: https://api.dropboxapi.com/2/files/list_folder via curl, I get a valid response.

If I make exactly the same request using Tesla (https://github.com/teamon/tesla) I get a 503 response returned by the server.

This is using exactly the same access token and parameters on the same machine over the same network request.

An example "x-dropbox-request-id" is "4141da5a0fcb4b2d8192bc13d2d56a5b" if this is helpful for debugging.

Can you see any reason for this?

Find more posts tagged with

Developers

Comments

tlqip1

If helpful, the error message returned in the body of the request is: "upstream connect error or disconnect/reset before headers. reset reason: connection termination" and the problem has been ongoing for about a day now

Greg-DB

Thanks for the report. I wouldn't expect the same exact request to produce different results like this just based on using different client, but it's possible that the different clients are issuing the requests in slightly different ways perhaps, resulting in the issue. Are you able to print out the full raw HTTP request and response for each client? E.g., for curl, you can use the "-v" option to show most of this. I can't speak to what debug options are available for the other client though. Seeing the rest of that information may be helpful. Please redact the access token though.

In addition to that, can you share several more "x-dropbox-request-id" response header values for these 503 errors? (Due to some implementation details a single one isn't always sufficient for investigation.)