[Bug 669] New: request's character encoding "null" behind ajp13

http://dev.helma.org/bugs/show_bug.cgi?id=669

           Summary: request's character encoding "null" behind ajp13
           Product: Helma
           Version: CVS trunk
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Web Support
        AssignedTo: helma-dev@...
        ReportedBy: nostalgiker@...


req.getServletRequest().getCharacterEncoding() is always null if the request
comes in via apache (mod_jk 1.2.26-2, i also tried the next two older versions
of mod_jk).

i would expect it to be the header's content-type encoding, e.g. for

 Content-Type: application/x-www-form-urlencoded; charset=UTF-8

it should be utf-8.

this problem existed with jetty5, still persists with current trunk and jetty6.

--
Configure bugmail: http://dev.helma.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Helma-dev mailing list
Helma-dev@...
http://helma.org/mailman/listinfo/helma-dev

http://dev.helma.org/bugs/show_bug.cgi?id=669





--- Comment #1 from s o <nostalgiker@...>  2009-06-17 16:47:20 ---
usually this is not a problem, since the request-encoding is supposed to be the
same as the response's.

we only noticed the problem with ajax-post-requests (always utf-8 encoded)
which where coming in garbled if app.charset=ISO-8859-15.

doing req.params.foo.toCharset("UTF-8") restored order.

--
Configure bugmail: http://dev.helma.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Helma-dev mailing list
Helma-dev@...
http://helma.org/mailman/listinfo/helma-dev