Bug report #388 has just been filed.

You can view the report at the following URL:

   <http://znutar.cortexity.com:8888/BugRatViewer/ShowReport/388>

REPORT #388 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: medium
Severity: serious
Confidence: public
Environment: 
   Release: 3.1
   JVM Release: 1.2.2
   Operating System: Linux
   OS Release: RedHat 6.2
   Platform: Intel

Synopsis: 
GET header defaults to be iso-8859-1 encoded which breaks intl' forms passed by GET

Description:
In org.apache.tomcat.service.http.Constants, CharacterEncoding.Default is used to 
specify the supposed encoding of request URI. while I understand, that this is 
standard it completely disallows forms with non-8859-1 characters to be sent and 
processed via GET. It would be nice to be able to specify this encoding on at least 
per-system basis, it would be cool to be able to set this encoding on per-context 
basis, but i'm afraid, that by the time of decoding URI, the servlet is not yet known, 
since it is choosen on the URI basis ;-))
Title: BugRat Report # 388

BugRat Report # 388

Project: Tomcat Release: 3.1
Category: Bug Report SubCategory: New Bug Report
Class: swbug State: received
Priority: medium Severity: serious
Confidence: public

Submitter: Skopal Jakub ( [EMAIL PROTECTED] )
Date Submitted: Nov 15 2000, 10:13:20 CST
Responsible: Z_Tomcat Alias ( [EMAIL PROTECTED] )

Synopsis:
GET header defaults to be iso-8859-1 encoded which breaks intl' forms passed by GET
Environment: (jvm, os, osrel, platform)
1.2.2, Linux, RedHat 6.2, Intel

Additional Environment Description:

Report Description:
In org.apache.tomcat.service.http.Constants, CharacterEncoding.Default is used to specify the supposed encoding of request URI. while I understand, that this is standard it completely disallows forms with non-8859-1 characters to be sent and processed via GET. It would be nice to be able to specify this encoding on at least per-system basis, it would be cool to be able to set this encoding on per-context basis, but i'm afraid, that by the time of decoding URI, the servlet is not yet known, since it is choosen on the URI basis ;-))

View this report online...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to