Recently we've been getting text/html 429 responses from the get_metadata endpoint, when we specify Accept: application/json header. Response: {:request=>{:url=>"https://api.dropboxapi.com/2/", :endpoint=>"files/get_metadata", :body=>"{\"path\":\"/myfolder\",\"include_deleted\":true}"}, :response=>{:code=>429, :body=>" \n \n \n Dropbox - 4xx \n \n \n\n \n \n \n \n \n \n Error (4xx) We can't find the page you're looking for. Here are a few links that may be helpful: * Home * Help center * Sign in * Get a free account * Dropbox Plus * Dropbox Business \n \n\n \nmessage = {\"ru\": \"\\u003cdiv class=\\\"not-found\\\"\\u003e \\u003ch1... Is there a reason why we're getting a text/html response instead of a json response?

Child Item

API get_metadata returns 429 text/html

Recently we've been getting text/html 429 responses from the get_metadata endpoint, when we specify

Accept: application/json

header.

Response:

{:request=>{:url=>"https://api.dropboxapi.com/2/", :endpoint=>"files/get_metadata", :body=>"{\"path\":\"/myfolder\",\"include_deleted\":true}"}, 

:response=>{:code=>429, :body=>"<!DOCTYPE html>\n<html>\n<head><meta http-equiv=\"Content-Type\" content=\"text/html; charset=utf-8\">\n<title>Dropbox - 4xx</title>\n<link href=\"https://cfl.dropboxstatic.com/static/css/error.css\" rel=\"stylesheet\" type=\"text/css\"/>\n<link rel=\"shortcut icon\" href=\"https://cfl.dropboxstatic.com/static/images/favicon.ico\"/>\n\n</head>\n<body>\n<div class=\"figure\">\n<img src=\"https://cfl.dropboxstatic.com/static/images/illustration_catalog/404_error-illo.png\" srcset=\"https://cfl.dropboxstatic.com/static/images/illustration_catalog/404_error-illo@2x.png 2x\" alt=\"Error: 4xx\"/>\n</div>\n<div id=\"errorbox\">\n<div class=\"not-found\"> <h1>Error (4xx)</h1> We can't find the page you're looking for. <div class=\"not-found--links\"> Here are a few links that may be helpful: <ul> <li><a href=\"https://www.dropbox.com/home?_tk=fof\">Home</a></li> <li><a href=\"https://www.dropbox.com/help?_tk=fof\">Help center</a></li> <li><a href=\"https://www.dropbox.com/login?_tk=fof\">Sign in</a></li> <li><a href=\"https://www.dropbox.com/register?_tk=fof\">Get a free account</a></li> <li><a href=\"https://www.dropbox.com/plus?_tk=fof\">Dropbox Plus</a></li> <li><a href=\"https://www.dropbox.com/business?_tk=fof\">Dropbox Business</a></li> </ul> </div> </div>\n</div>\n\n<script>\nmessage = {\"ru\": \"\\u003cdiv class=\\\"not-found\\\"\\u003e \\u003ch1...

Is there a reason why we're getting a text/html response instead of a json response?

Find more posts tagged with

API

Abuse

Accepted answers

Greg-DB

To follow up here, the team confirmed that they found and resolved the issue with the excessive 429 responses with HTML bodies as of late Friday. Apologies for the inconvenience.

All comments

Greg-DB

Thanks for the report. It looks like we may be using a generic HTML error page in some rate limiting cases. We'll look into it.

jeji

Thanks, keep me posted please!

UlfFahlen

We're having the same issue. Suddenly some of our internal applications are crashing due to this. It disrupts our work very seriously. I dont feel me made any abusive calls.

Our apps are set in "development" status and used only by ourselves.

Greg-DB

@jeji I'll follow up on this thread once I have an update on this.

Greg-DB

@UlfFahlen Thanks for the additional report. We're looking into it. Note that the development/production status of your app wouldn't affect this.

UlfFahlen

The problems have arised when checking if a file exists on dropbox. In our SDK:

$dropbox->has($file)

This calls get_metadata on the API.

We used this to determine if a file existed before uploading or deleting it. We have removed it from our script now and instead added an exception to handle the errors when trying to delete a file already deleted. The script now works, but the rate limit set on this API call is very limiting (and new).

Fotosprint

We're having a similar issue.

Some requests to different endpoints are returning 429, that's may be normal due to rate limit.

But before, Retry-After header was returned, and we waited that time before retrying another request.

Now, Retry-After isn't present and we don't know exactly how long to wait before retrying or continuing the upload.

Greg-DB

To follow up here, the team confirmed that they found and resolved the issue with the excessive 429 responses with HTML bodies as of late Friday. Apologies for the inconvenience.