> > None of headers in response are supposed to be changed between requests
> > except Date.
>
> Sure, if it's just a static response and there's no content-negotiation
> going on.
I don't think, anyone in his right mind will let in-kernel server do
anything else.
> > > I'm not that happy about getting things like "building a
> > > Date: Header with time zone and everything" in the kernel.
> >
> > It's in GMT, and IMHO can be omitted. And userspace application can feed
> > parameters to the kernel just like what is used for kmod.
>
> If you intend to implement HTTP, and you intend to use the Last-Modified
> or Expires headers, then you MUST include a Date header. See rev-06 of
> the update to rfc2068 for more clarification.
This is not the only flaw in HTTP 1.1 design.
> And given that static responses are the best places where Last-Modified
> and Expires can be used... it seems silly to omit them.
Unless the whole thing supports HTTP 1.0 with extensions instead of
HTTP 1.1 -- then Date requirement is without that "MUST".
-- Alex---------------------------------------------------------------------- Excellent.. now give users the option to cut your hair you hippie! -- Anonymous Coward
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/