Verify maxHeaderSize defaults across Harper HTTP configuration references

Ouverte
#742 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 4 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
1-2 jours
Accessibilité débutants
52/100
Type d'issue
Documentation
Clarté
Clairement spécifiée
Activité
Active
Stack technique
node.js
Domaine
documentation

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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)

Langage dominant
MDX
Étoiles
9
Forks
9
Merge moyen
5 j 5 h
PR mergées (30 j)
48

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de HarperFast/documentation

Toutes les issues de HarperFast/documentation

Issues similaires

Plus d'issues Documentation

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.