René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"http.ServerResponse#sendDate makes overly definitive claim about HTTP standards","articleBody":"### Affected URL(s)\n\nhttps://nodejs.org/docs/latest-v16.x/api/http.html#responsesenddate\n\n### Description of the problem\n\nFrom the docs on this parameter:\r\n\r\n\u003e This should only be disabled for testing; HTTP requires the Date header in responses.\r\n\r\nHowever, the story seems to be a bit more complicated than that; [RFC 7231](https://httpwg.org/specs/rfc7231.html#header.date) has a rather dense paragraph which can be summarized as:\r\n* Server MUST NOT send Date if it doesn't have a suitable clock\r\n* Server MAY send Date for 1xx or 5xx statuses\r\n* Server MUST send Date otherwise (i.e. it has a clock and is sending 2/3/4xx)\r\n\r\nThis note appears to have been added along with the setting itself in 1e425e3fa774fefd3553ecaa6f0ac35f9b0a1355, which doesn't provide any insight on where this claim originated.\r\n\r\nI'm not an expert on either Node or HTTP, but it seems like maybe the docs should be updated to something like the below?\r\n\r\n\u003e This should generally be left enabled; the Date header is mandatory in most cases. (See [RFC 7231](https://httpwg.org/specs/rfc7231.html#header.date) for details.)","author":{"url":"https://github.com/wolfgang42","@type":"Person","name":"wolfgang42"},"datePublished":"2022-04-06T04:28:16.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/42619/node/issues/42619"}