diff options
| author | Pjotr <wrk@bosa.lan> | 2026-11-08 12:38:02 +0000 |
|---|---|---|
| committer | Pjotr <wrk@bosa.lan> | 2026-11-08 12:38:02 +0000 |
| commit | b8fdbb3d60603c07cacf9f406ed1a5c228223829 (patch) | |
| tree | 10fe8f955bf4ce40b4317b030a999d4f80736e7a /test/python/server_test_case.py | |
| parent | c008bdeca126062b2ab87bb82e7fc9ae05060e5f (diff) | |
| download | genenetwork4-b8fdbb3d60603c07cacf9f406ed1a5c228223829.tar.gz | |
http: accept bodies up to 64 MiB, not axum's 2 MiB default
A caller posting a mapping result back to /plot/rqtl -- or a compute
request carrying a value per individual plus covariates -- was refused
with `413 Failed to buffer the request body: length limit exceeded`. That
is axum's DefaultBodyLimit, 2 MiB, which nothing here had raised: a real
GEMMA run on the BXD WGS panel is ~1.9 MB, so the plot endpoints sat just
under the cap and anything bigger (a genome-sized run, or every animal's
covariate value) fell over it. nginx's 10m was never the binding limit.
* src/lib.rs (BODY_LIMIT_BYTES): 64 MiB, with the reasoning and the note
that a proxy has to allow as much or it refuses first.
* etc/nginx-vesuvio.pu.ac.ke.conf, docs/nginx.md: client_max_body_size
64m, so the two limits agree instead of the proxy cutting in at 10m.
* README.md ("Request body size"): both caps, and that a request does not
need to be large -- `{"case_attribute": "Sex"}` has the server read the
attribute and align it, where posting a value per animal is pure payload.
Verified: the 11.9 MB body that was refused now returns an SVG; 67 MB
still gets axum's 413.
Diffstat (limited to 'test/python/server_test_case.py')
0 files changed, 0 insertions, 0 deletions
