The following reply was made to PR mod_mime/1559; it has been noted by GNATS.
From: Gordan Vosicki <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: mod_mime/1559: Language negotiation requires the language name to follow all the rest. Date: Wed, 17 Dec 1997 12:31:19 +0100 [EMAIL PROTECTED] wrote: > [In order for any reply to be added to the PR database, ] > [you need to include <[EMAIL PROTECTED]> in the Cc line ] > [and leave the subject line UNCHANGED. This is not done] > [automatically because of the potential for mail loops. ] > > Synopsis: Language negotiation requires the language name to follow all the > rest. > > State-Changed-From-To: open-feedback > State-Changed-By: pcs > State-Changed-When: Tue Dec 16 03:12:44 PST 1997 > State-Changed-Why: > Hello. Can you explain why you think that this does > not work? If you telnet to your server and request > the page do you see a "Content-Language" header? > Can you put both of these files on a server which we > can access, for tesing? It doesn't work because when the file is called "index.html.fr", then I get it andwhen it is called "index.fr.html", then I don't. Apache returns the "Content-Language" header the right way. If my french file is called index.html.fr, the Content-language is fr. If my file is called index.fr.html and I have a file index.html.en (english is my 2nd choice), then I get a Content-language: en with the english document. If my english document is called index.en.html, the server does not find the document. > > > It should work. Extensions (such as "en" and "html") can be > given in ANY order. Obviously Apache has to be told > about the extension for it to understand them (with, > for example, AddType and AddLanguage). Obviously, I have 3 AddLanguage statements. Hope it helps Gordan Vosicki
