Child Item

The remote server returned an error: (414) Request-URI Too Large.

I'm using the current end point to retrieve a users folders and files:

https://www.dropbox.com/developers-v1/core/docs#delta

I get the following error The remote server returned an error: (414) Request-URI Too Large. the cursor returned from the end point is 31279 characters in length the entries count: 2000 I've tried to reproduce this but can't Do you know why this might be occuring ?

Thanks

Find more posts tagged with

API

Abuse

Accepted answers

Greg-DB

Hi Ashley, the cursor can get very large like this when the account has many shared folders. The 414 error indicates that the URI (including the parameters, in this case, the long cursor) is too long to be processed.

Instead, you can include the parameters in the body of the API call, not on the URI itelf. For example, in curl, that would mean instead of doing something like this:

curl -X "POST" "https://api.dropboxapi.com/1/delta?cursor=CURSOR_HERE" \
    -H "Authorization: Bearer ACCESS_TOKEN_HERE"

you would do something like this:

curl -X "POST" "https://api.dropboxapi.com/1/delta" \
    -H "Authorization: Bearer ACCESS_TOKEN_HERE" \
    --data "cursor=CURSOR_HERE"

(Also, I should note that API v1 is deprecated, so we recommend migrating to API v2 as soon as possible.)

All comments

Mark

*moves to API forum*

Greg-DB

Instead, you can include the parameters in the body of the API call, not on the URI itelf. For example, in curl, that would mean instead of doing something like this:

curl -X "POST" "https://api.dropboxapi.com/1/delta?cursor=CURSOR_HERE" \
    -H "Authorization: Bearer ACCESS_TOKEN_HERE"

you would do something like this:

curl -X "POST" "https://api.dropboxapi.com/1/delta" \
    -H "Authorization: Bearer ACCESS_TOKEN_HERE" \
    --data "cursor=CURSOR_HERE"

(Also, I should note that API v1 is deprecated, so we recommend migrating to API v2 as soon as possible.)

Ashley B.15

Thanks. One other quick question. What is the best/prefered way for a desktop application to retrieve all users folders and files? Is it the deleta or metadata endpoint in v1 api?

I did move to v2 api but still waiting on feedback for this post :

https://www.dropboxforum.com/t5/API-support/500-internal-Server-Error-https-api-dropboxapi-com-2-files-list/m-p/181623#M7493

Thanks again

Greg-DB

In API v1, /delta is preferred for listing all files and folders.