Project

General

Profile

Actions

Bug #7645

closed

[Documentation] client_max_body_size needs to be set consistently through nginx

Added by Brett Smith over 8 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Documentation
Target version:
Story points:
0.5

Description

nginx's default client_max_body_size is 1MB. This means you can't create API objects larger than that, which is a limit you'll hit quickly in collections.

Our API server install guide suggests you set client_max_body_size to 128m, but only in the API server front-end section. It needs to be set consistently everywhere it matters, like the API server backend server.

If it makes sense, you could just set it in the top section of the configuration (the http section), but that's probably not wise since other servers like Websockets don't need it.

Make sure client_max_body_size is set consistently for nginx in the install guide.


Subtasks 1 (0 open1 closed)

Task #7742: Review branch 7645-doc-client-max-body-size-wipResolvedNico César11/09/2015Actions
Actions #1

Updated by Brett Smith over 8 years ago

  • Target version set to Arvados Future Sprints
Actions #2

Updated by Brett Smith over 8 years ago

  • Status changed from New to In Progress
  • Assigned To set to Brett Smith
  • Target version changed from Arvados Future Sprints to 2015-11-11 sprint
Actions #3

Updated by Brett Smith over 8 years ago

  • Target version changed from 2015-11-11 sprint to 2015-12-02 sprint
Actions #4

Updated by Nico César over 8 years ago

rev 7869b5de683d77e8fe128ea6cdaf43a473853a81

I try to come up if there is a good reason any other number than 50m in doc/install/install-arv-git-httpd.html.textile.liquid but I couldn't. all the other changes sound reasonable

LGTM

Actions #5

Updated by Brett Smith over 8 years ago

  • Status changed from In Progress to Resolved

Applied in changeset arvados|commit:d3171a9d75eac20b68cee6729dddc28cd7e6c612.

Actions

Also available in: Atom PDF