Thanks for explaining the spec and the suggestions. I saw your post on the dev list. I don't want to side track that thread so I was wondering if you could point me to the workaround you mentioned if the client only specified one language. Thanks in advance. , Josh. > -----Original Message----- > From: jslive@xxxxxxxxx [mailto:jslive@xxxxxxxxx] On Behalf Of > Joshua Slive > Sent: Friday, December 08, 2006 1:18 PM > To: users@xxxxxxxxxxxxxxxx > Subject: Re: Multiviews Problem > > On 12/8/06, Fenlason, Josh <jfenlason@xxxxxxx> wrote: > > You're correct. I can manually type in just the language > code. I'm > > not sure I'll be able to require our customers to do that, > but thanks > > for the suggestion. > > I haven't read the spec myself. According to the spec the server > > isn't supposed to be allowed to fall back to the language if it > > doesn't have content specific for the language and country. > Is that > > right? That would seem less than ideal to me, but I'm sure > those who > > wrote the spec are smarter than myself. > > Yes, it is very clear that if the client asks for "en", then > the server can send "en-gb" in response. But if the client > asks for "en-gb", the server is not allowed to send "en". > This is not inherently a problem. It simply leaves all the > flexibility in the clients hands. A client who sends "en-gb" > should also send "en" (with a lower quality value) to > indicate that he prefers british english but will take any > other english variant if necessary. It is setup this way to > allow reasonable configurations like "fr-fr;q=0.9, en;q=0.8, > fr;q=0.7" for a person who prefers french from france to > english, but has a harder time understanding other variants of french. > > > If that's what it says, then shame on MS for going out of > their way > > to blatantly disobey it. > > Yes, the only explanations I can see are that they are either > responding to a buggy implementation in IIS, or they just > didn't bother to read the spec at all. > > > In order to use type-maps to server de* with .de file do I have to > > spell out all the de-<country> variations in the > Content-language directive? > > Or is there a way to do this more dynamically? Thanks. > > Yes, I believe you'll need to list every possible variant. > > Feel free to bring this issue up on the dev list if you'd > like. With MS putting a flood of broken browsers into the > wild, someone might be willing to revisit adding a > spec-breaking option to work around them. > > Joshua. > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP > Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|