OK, it seems that tomcat is working correctly.
Still I would like to get the root cause of my problem which is again:
The last-modified response header is delivered in the locale of the
server. E.g. if this locale is polish or germen, the header is delivered
in polish resp. german format which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 12/18/2009 5:32 AM, Mark Thomas wrote:
> On 18/12/2009 08:41, Abid Hussain wrote:
>> Hi,
>>
>> I'm using Tomcat 6.0.20, installed on a german Windows XP.
>>
>> I'm quite sure that the cause is tomcat's code.
>
> And I'm quite sure it isn't.
Hi again,
It seems that Mark is right. I just tried it with another webapp and
also in a clean installation and the headers are correct there, even if
the locale is set to polish.
Have to investigate further what causes the misspelled header. There
aren't any filters in my webapp that modify t
On 18/12/2009 08:41, Abid Hussain wrote:
> Hi,
>
> I'm using Tomcat 6.0.20, installed on a german Windows XP.
>
> I'm quite sure that the cause is tomcat's code.
And I'm quite sure it isn't. I have tested trunk, 6.0.x and 6.0.20 and
all behave correctly.
> When I use e.g. for
> startup polish
Hi,
I'm using Tomcat 6.0.20, installed on a german Windows XP.
I'm quite sure that the cause is tomcat's code. When I use e.g. for
startup polish locale:
-Duser.language=pl
-Duser.region=PL
Tomcat delivers the Last-Modified header in polish:
Pt, 18 gru 2009 08:33:49 GMT
The Date header is alway
