Bug 50848 - Content Negotiation type map file precedence could be clarified
Summary: Content Negotiation type map file precedence could be clarified
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Documentation (show other bugs)
Version: 2.5-HEAD
Hardware: All All
: P2 enhancement with 3 votes (vote)
Target Milestone: ---
Assignee: HTTP Server Documentation List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-01 10:48 UTC by Fiable.biz
Modified: 2013-08-18 03:56 UTC (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fiable.biz 2011-03-01 10:48:44 UTC
On page
http://httpd.apache.org/docs/current/en/content-negotiation.html#negotiation
it's written “ a typemap file will take precedence over the filename's extension, even when Multiviews is on.”
This could be a bit detailed.
1) If there are both foo.html and foo.html.var files and the latter doesn't mention the former, is foo.html ignored?
2) If Multiviews in on and there is a foo.var file saying
  URI: foo

  URI: foo.en.html
  Content-type: text/html
  Content-language: en

  URI: foo.fr.de.html
  Content-type: text/html;charset=iso-8859-2
  Content-language: fr, de

and a foo.mn.html file, is this one served to a browser requiring Mongolian language, or is it ignored because not mentioned in foo.var ?
This is a quite important point for websites becoming international. They used to be of one language and not to use any language extension in file names, like foo.html . Since "Cool URI don't change" (Tim Berners-Lee), such files should not be renamed but rather assigned their particular language in the typemap file. But is it for that required to describe the map of all other variant files, named with a language extension, like foo.mn.html ?
Comment 1 Christoph Anton Mitterer 2013-08-18 03:56:20 UTC
Moving this to HEAD, as it's still very badly and not understandably documented.