Anonymous | Login | Signup for a new account | 12-17-2024 12:01 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0002180 | [Resin] | minor | always | 11-16-07 13:31 | 11-29-07 17:58 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | Platform | |||||
Status | closed | OS | |||||||
Projection | none | OS Version | |||||||
ETA | none | Fixed in Version | 3.1.4 | Product Version | 3.1.3 | ||||
Product Build | |||||||||
Summary | 0002180: i18n response.getCharacterEncoding | ||||||||
Description |
(rep by Takahiro Fukuda) [Phenomenon] When the character encoding of ServletResponse is not set, ServletResponse#getCharacterEncoding() returns null. (The phenomenon was confirmed with Resin3.1.3) [Question] Is this phenomenon a bug? In API list of J2EE1.4, it is described as follows. Explicit specifications take precedence over implicit specifications. If no charset is specified, ISO-8859-1 will be used. I think, When the character encoding of ServletResponse is not set, ServletResponse#getCharacterEncoding() should return "ISO-8859-1". -- |
||||||||
Steps To Reproduce | |||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
30 total queries executed. 26 unique queries executed. |