cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Want to learn some quick and useful tips to make your day easier? Check out how Calvin uses Replay to get feedback from other teams at Dropbox here.

Dropbox API Support & Feedback

Find help with the Dropbox API from other developers.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

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

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

Ashley B.15
Helpful | Level 7
Go to solution

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

1 Accepted Solution

Accepted Solutions

Greg-DB
Dropbox Staff
Go to solution

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.)

 

 

View solution in original post

4 Replies 4

Mark
Super User II
Go to solution
*moves to API forum*

 


:penguin::penguin: - :penguin: - :penguin: - :penguin:


Heart Did this post help you? If so please mark it for some Kudos below. 


:white_check_mark: Did this post fix your issue/answer your question? If so please press the 'Accept as Solution' button to help others find it.


:arrows_counterclockwise: Did this post not resolve your issue? If so please give us some more information so we can try and help - please remember we cannot see over your shoulder so be as descriptive as possible! 


 

Greg-DB
Dropbox Staff
Go to solution

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.)

 

 

Ashley B.15
Helpful | Level 7
Go to solution

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-fil...

 

Thanks again

Greg-DB
Dropbox Staff
Go to solution
In API v1, /delta is preferred for listing all files and folders.
Need more support?