Document http.maxRequestBodySize (REST, MCP application endpoint, and operations API body limits)

Abierto Apto para principiantes
#806 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 4 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
88/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo

Línea de trabajo

Empieza por reference/configuration/options.md y documenta http.maxRequestBodySize y operationsApi.network.maxRequestBodySize usando los valores predeterminados y el comportamiento de herencia descritos en el issue. Después, añade la nota sobre el límite del cuerpo de MCP a reference/mcp/overview.md y comprueba dónde está la nota existente sobre la limitación de velocidad para decidir su ubicación. El trabajo estará terminado cuando los tres puntos de aplicación y la salvedad de versión indicada estén documentados correctamente.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Re-verified on harper main a7dae444c (2026-10-26). Correction to the version note below: MCP application-endpoint enforcement merged as harper#3398 on 2026-10-26 and ships in 5.4; the v5.3 cherry-pick (harper#3536) is still open, so say "5.4 (and 5.3.x once #3536 ships)" rather than 5.3.1. Re-checked against harper main a7dae444c: the three enforcement points are unchanged. Related: harper#3397 (bound the discard of a rejected body).

What is missing

http.maxRequestBodySize does not appear anywhere in the documentation tree (git grep -i maxrequestbody at origin/main 34b029d9 → 0 hits). reference/configuration/options.md:156 lists the operationsApi: block without network.maxRequestBodySize; reference/mcp/configuration.md and reference/mcp/overview.md say nothing about a request-body limit.

What the code does (harper main 0c94b150b)

One option, three enforcement points:

  • REST / any streamToBuffer reader — server/serverHelpers/contentTypes.ts:618 reads http_maxRequestBodySize (default 10,000,000 bytes); :626-634 answers 413 Request body too large, maximum size is N bytes.
  • MCP application endpoint — since PR #3398 (f0f4e5007, 5.3.1): components/mcp/adapters/harperHttp.ts:68,117-137 refuses a declared Content-Length over the limit before any byte arrives and a streamed body once the running count exceeds it, 413 {"error":"payload_too_large","message":…}.
  • Operations API — Fastify bodyLimit from operationsApi.network.maxRequestBodySize (server/operationsServer.ts:50,368, default 1 GiB), which config/configUtils.ts:1228 fills from http.* whenever the operationsApi.network block exists — and the shipped static/defaultConfig.yaml:62-69 always ships that block. So setting http.maxRequestBodySize also caps the operations API unless operationsApi.network.maxRequestBodySize is set separately.

Measured (SQA-73/SQA-74): with http.maxRequestBodySize: 65536, a REST PUT, an MCP POST on the application port and an MCP POST on the operations port all refuse at 65,537 bytes; with it unset, the operations port accepts up to 1 GiB.

Suggested content

In reference/configuration/options.md, under http: maxRequestBodySize — bytes, default 10000000; applies to REST and custom resources, and to the MCP application endpoint (5.3.1+); exceeding it returns 413. Under operationsApi.network: maxRequestBodySize — default inherits http.maxRequestBodySize when set, otherwise 1 GiB. One line in reference/mcp/overview.md beside the existing note that global rate limiting does not apply to MCP, stating that the body limit does.

Existing work checked

HarperFast/documentation issues and PRs searched for maxRequestBodySize and body size: nothing (open docs PRs #745, #739, #734 are credential masking, full-text paging, MCP subscribe). harper 1,500 issues + 800 PRs and harper-pro 349 + 768 titles: PR #3398 (merged) and harper#3397 (open, discard bound) name the key only in code terms; #3398 cites components/mcp/DESIGN.md, not the docs repo.

What this does not prove

A docs change in flight on a branch other than origin/main as of 34b029d9 (fetched 2026-10-26T04:10Z); the operations-port fallback for a hand-edited config with no operationsApi.network block (source read only, not measured).

Lenguaje dominante
MDX
Estrellas
9
Forks
9
Merge medio
5 d 5 h
PR fusionados (30 d)
48

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de HarperFast/documentation

Todos los issues de HarperFast/documentation

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.