Return-Path: owner-new-httpd Received: by taz.hyperreal.com (8.6.10/8.6.5) id JAA25305; Thu, 16 Mar 1995 09:07:01 -0800 Received: from paris.ics.uci.edu by taz.hyperreal.com (8.6.10/8.6.5) with SMTP id JAA25296; Thu, 16 Mar 1995 09:06:58 -0800 Received: from avron.ics.uci.edu by paris.ics.uci.edu id aa16932; 16 Mar 95 9:03 PST To: new-httpd@hyperreal.com Subject: Re: content negotiation In-reply-to: Your message of "Wed, 15 Mar 1995 13:45:38 EST." <9503151845.AA03760@volterra> Date: Thu, 16 Mar 1995 09:03:28 -0800 From: "Roy T. Fielding" Message-ID: <9503160903.aa16932@paris.ics.uci.edu> Sender: owner-new-httpd@hyperreal.com Precedence: bulk Reply-To: new-httpd@hyperreal.com rst writes: > NB I'm not sure whether the right thing for language is to handle it > as a separate header in the extended format, or simply to have it as a > lang= parameter in the mapped MIME types; the answer is presumably in > the MIME RFCs. Roy, any thoughts? It's in the latest HTTP/1.0 spec -- Accept-Language and Content-Language. The only thing that appears in a Content-type is a ;vary="lang" if variants exist at that URL with different Content-Language values. > Unresolved issues here are how to specify matches to the User-agent: > header (initial substrings to match? Full regex's --- and using whose > library if so? Something else?) That is a nontrivial problem and generally only handled within scripts. I would avoid it like the plague (for now). ......Roy