On Tue, Feb 7, 2012 at 2:57 PM, Matt <[email protected]> wrote: > On Tue, Feb 7, 2012 at 2:54 PM, Ben Noordhuis <[email protected]> wrote: > >> On Tue, Feb 7, 2012 at 18:47, Martin Cooper <[email protected]> wrote: >> > On Mon, Jan 30, 2012 at 8:34 PM, Martin Cooper <[email protected]> >> wrote: >> >> As mnot pointed out in pull request #311 (back in Sep 2010), date >> >> headers are required in responses. The pull request addressed that, >> >> and it looked like it was merged in. But if it was, it seems to have >> >> fallen off again somewhere along the line, because there's no sign of >> >> date header handling in the http module. >> >> >> >> What's the story on this? Can we get this added (back) in? >> > >> > Anyone? It seems to me that this is important functionality that's >> > currently missing from Node (and is entirely appropriate for core). >> >> I lean towards 'no'. I like the low-level nature of the http module. >> If people want to add a Date header, they can do so manually or have >> their web framework of choice do it for them. >> > > If people want to get so low level they can break the spec they should > just use net.createServer(), no? >
It's pretty easy to break the spec. Do you really want node ensuring we * never* serve invalid HTTP? That seems like a fool's errand. If it *keeps* us from serving an otherwise valid HTTP request (e.g. such as limiting the request methods to a specific list :) we should care, but not the other way around.
