You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2001/12/18 13:20:38 UTC
DO NOT REPLY [Bug 5483] New: -
I18N fails using AJP 1.3 with Tomcat 4.01 final / Apache 1.3.22
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5483>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5483
I18N fails using AJP 1.3 with Tomcat 4.01 final / Apache 1.3.22
Summary: I18N fails using AJP 1.3 with Tomcat 4.01 final / Apache
1.3.22
Product: Tomcat 4
Version: 4.0.1 Final
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Critical
Priority: Other
Component: AJP Connector
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: a.augustin@ceyoniq.com
Overview Description:
I18N of web app based on ACCEPT_LANGUAGE header fails with AJP 1.3 and Tomcat
4.01 final / Apache 1.3.22. ACCEPT_LANGUAGE value is *ignored* instead the
default location of the Java runtime Tomcat is running in seems to be used
resulting in the deliverance of always the same language regardless of the
browser�s HTTP request.
Steps to reproduce:
Just create a minimal web app consisting of one JSP which *prints* the language
settings. Regardless of the HTTP request it seems to be always the Java runtime
default setting.
Actual results:
Web app always delivers its contents in the same language regardless of the
requested language and the available language resources.
Expected result:
Web app should deliver its content in the requested language falling back to
its default language if no suitable language resources were found.
Build date & platform:
Tomcat 4.01 final / AJP 1.3 / Apache 1.3.22 running on NT 4 SP 6
IE 4.0 to IE 6 with latest respective SPs and NN 4.78, NN 6.01 and NN 6.02 as
browser platforms.
Additional information:
We *cross-tested* the mentioned minimal web app with all mentioned browsers
(vendors and versions) and the described behaviour was ALWAYS reproducible.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>