Bug 32622 - timefmt ignored for LAST_MODIFIED etc when no language code in filename
Summary: timefmt ignored for LAST_MODIFIED etc when no language code in filename
Status: RESOLVED DUPLICATE of bug 39369
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_include (show other bugs)
Version: 2.0.52
Hardware: Sun Solaris
: P4 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-10 01:04 UTC by Edgar Hoch
Modified: 2007-08-24 10:29 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Edgar Hoch 2004-12-10 01:04:42 UTC
When using auto negotation then timefmt seems to be ignored.
I use the following sequence:

<!--#config timefmt="%d.%m.%Y" --><!--#echo var="LAST_MODIFIED" -->

The files are named like file.html.de and file.html.en, the first declares
<meta name="content-language" content="de">, the second
<meta name="content-language" content="en">. I know that the meta
content-language tag is not interpresed by the httpd server.

When I call http://server/file.html.de or http://server/file.html.en
then all works as expected. The date is shown by both files
in the requested format (e.g. 10.12.2004).
But if I call http://server/file.html then because of my browsers (mozilla)
preferences the file.html.de page is shown. The date is expected in the
same format as before, but it is shown in the standard 'C' format
(e.g. 10-Dec-2004 00:02:34 MET).

The same happens if I copy file.html.de to file.html and then view it in the
Browser.

I suggest that when using 'timefmt' the shown date format should depend on
'timefmt', not on the way the file is selected (e.g. by name or by negotiation).
It should only depend on the language set if no timefmt is specified.
It should always use 'timefmt'.
Could you please fix it?

Many thanks in advance.
Comment 1 Joshua Slive 2007-08-24 10:29:41 UTC
Actually, the other bug is a dupe. But it has slightly more info and tests with
a newer version so I'm closing this one.

*** This bug has been marked as a duplicate of 39369 ***