Re: Handling multiple headers when only one is allowed

> As an aside -- I'm curious about the "they tend not to focus on such earthly things" characterisation. On what basis was that impression formed?

Sorry, that was not meant to be inflammatory; historically, HTTP specs
would either explicitly or implicitly steer clear of most
implementation-level security topics (e.g., header charsets,
precedence, caching header conflict resolution, etc). If that's not
the intention anymore, good.

/mz