|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 2180 | minor | always | 11-16-07 13:31 | 11-29-07 17:58 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 3.1.3 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.1.4 | ||
|
|
|||||
| 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: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||