Bug report #530 has just been filed. You can view the report at the following URL: <http://znutar.cortexity.com/BugRatViewer/ShowReport/530> REPORT #530 Details. Project: Tomcat Category: Bug Report SubCategory: New Bug Report Class: swbug State: received Priority: medium Severity: serious Confidence: public Environment: Release: 3.2-final JVM Release: n/a Operating System: n/a OS Release: n/a Platform: n/a Synopsis: [PATCH] bad default character encoding in jsp pages Description: jsp pages served by tomcat contain a bad charset string in their http header. This is not understood by some non iso8859-1 systems/browsers. Macintosh w/ netscape 4.76 will fail to understand that 8859_1 is actually ISO-8859-1. According to src/webpages/docs/api/javax/servlet/ServletResponse.html, the reply should be "ISO-8859-1". According to IANA, the 8859_1 is *not* a way to say ISO-8859-1 in MIME headers <http://www.isi.edu/in-notes/iana/assignments/character-sets> Name: ISO_8859-1:1987 [RFC1345,KXS2] MIBenum: 4 Source: ECMA registry Alias: iso-ir-100 Alias: ISO_8859-1 Alias: ISO-8859-1 (preferred MIME name) Alias: latin1 Alias: l1 Alias: IBM819 Alias: CP819 Alias: csISOLatin1 are all allowed ways to describe a character set in MIME. This is not the same as Java's internal represenation, which truely is 8859_1.Title: BugRat Report # 530
BugRat Report # 530
| Project: Tomcat | Release: 3.2-final |
| Category: Bug Report | SubCategory: New Bug Report |
| Class: swbug | State: received |
| Priority: medium | Severity: serious |
|
Confidence:
public
|
Submitter:
Palle Girgensohn ( [EMAIL PROTECTED] )
Date Submitted:
Dec 5 2000, 06:52:47 CST
Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )
- Synopsis:
- [PATCH] bad default character encoding in jsp pages
- Environment: (jvm, os, osrel, platform)
- n/a, n/a, n/a, n/a
- Additional Environment Description:
- Report Description:
-
jsp pages served by tomcat contain a bad charset string in
their http header. This is not understood by some non iso8859-1
systems/browsers. Macintosh w/ netscape 4.76 will fail to
understand that 8859_1 is actually ISO-8859-1.
According to
src/webpages/docs/api/javax/servlet/ServletResponse.html,
the reply should be "ISO-8859-1". According to IANA,
the 8859_1 is *not* a way to say ISO-8859-1 in MIME headers
- How To Reproduce:
- null
- Workaround:
- null
