Skip to content

doc: explain HTTP writeHead()'s fast path behavior

Rodrigo Muino Tomonari requested to merge github/fork/gireeshpunathil/header-persistence into master

calling writeHead() into a Response object that has no headers already set causes getHeader() to return undefined, even if the header was set in the writeHead() function call. Explain this behavior as an optimiation as opposed to a bug.

Fixes: https://github.com/nodejs/node/issues/10354

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines

Merge request reports