Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An action with more than ~250 nodes ends in 414 Request-URI Too Large #253

Open
raffis opened this issue Jul 10, 2019 · 1 comment
Open
Assignees
Labels
Milestone

Comments

@raffis
Copy link
Contributor

raffis commented Jul 10, 2019

Describe the bug

If one selects a total number of around ~250 nodes the request uri exceed 8000 characters and nginx will decline it with a 414.

To Reproduce

  1. Add 250 nodes to the trash
  2. Mark alll nodes and hit restore

Expected behavior

The client must split those requests into chunks of ~200 nodes.
(All requests which allow batching nodes. Download, Restore, Delete, Move, Copy, ...)

The server v3.0 will have a batch endpoint gyselroth/balloon#283 but even this endpoint will probably have a limit of actions and the client has to send multiple requests.

Environment

  • web-client version: v3.2.5
  • balloon server version: v2.6.1
  • Deployed as: [e.g. docker,deb package,tar,compiled manually]
  • client os: [e.g. Linux Mint 19.2]
  • browser: [e.g. Firefox 62]

Additional context

Add any other context about the problem here.

@raffis raffis added the bug label Jul 10, 2019
@raffis raffis added this to the v3.3.x milestone Jul 10, 2019
@raffis
Copy link
Contributor Author

raffis commented Oct 25, 2019

The easiest solution is most likely just to limit the max. selectable nodes to 100.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants