Verify maxHeaderSize defaults across Harper HTTP configuration references

Abierto
#742 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
4/5
Tiempo estimado
1-2 días
Aptitud para principiantes
52/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
node.js

Línea de trabajo

Start with the cited HTTP configuration references and Harper’s config-root.schema.json and server/http.ts at the linked revisions; verify unset and explicitly configured behavior across the supported HTTP entry points. Compare the effective values with the documented defaults, keeping the sample YAML’s value distinct if it is deliberate. Done when the evidence supports any corrected references and the sample is clearly identified as an example value.

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

Descripción

content

Verify the effective maxHeaderSize defaults before changing the HTTP configuration references. The stated defaults and sample use different values; an example may deliberately choose a value other than the default:

Node 24.16.0 reports require('node:http').maxHeaderSize === 16384. That alone does not establish the effective default for every Harper transport or runtime, so aligning the numbers without checking the server would risk preserving the wrong value.

Confirm the unset and explicitly configured behavior for the supported HTTP entry points. Correct the stated defaults or core schema description only if that evidence shows they are inaccurate. The sample need not match the default; distinguish a platform default from a deliberately chosen example value.

Found while reviewing Document full-text and autocomplete snapshot paging, which advises leaving header space for continuation tokens. This is a pre-existing accuracy question; the paging PR does not state a numeric header limit. No runtime failure or customer impact was observed.

Priority P3: contained documentation verification task with no observed runtime failure. Effort Low: verify the effective defaults and correct references only where necessary. No release is committed and no open documentation parent found in discovery owns HTTP-reference accuracy.

Comment generated by kAIle (GPT-6)

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.