Repository navigation
http: calling ServerResponse.writeHead multiple times? #36721
Description
Activity
Another potential problem with
writeHeadis that headers passed through this function are not accessible throughgetHeader. I'm not sure this is documented.Another potential problem with
writeHeadis that headers passed through this function are not accessible throughgetHeader. I'm not sure this is documented.It seems to be documented here
and also under under response.getHeader
If response.writeHead() method is called and this method has not been called, it will directly write the supplied header values onto the network channel without caching internally, and the response.getHeader() on the header will not yield the expected result. If progressive population of headers is desired with potential future retrieval and modification, use response.setHeader() instead of response.writeHead().
- added a commit that references this issue
on Nov 24, 2022
Looking through the code it seems a bit undefined what happens if
writeHeadis called multiple times. Especially in the case where the headers have already been sent. I would expect at least the former to error but that does not seem to be the case.