Jetty

POST Parameter Encoding Issue Upgrading from 6.1.11

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Not A Bug
  • Affects Version/s: 6.1.14
  • Fix Version/s: None
  • Component/s: HTTP
  • Labels:
    None
  • Environment:
    32-bit Windows XP, development environment, Jetty executed using maven-jetty-plugin, JDK1.6_06
  • Number of attachments :
    0

Description

I'm having an encoding issue after upgrading from Jetty 6.1.11 to Jetty 6.1.14. Text data submitted via POST no longer gets interpretted as UTF-8. If I post "Héy." the request object gives me "Héy."

I get the same problem with Jetty 6.1.12. Reverting to Jetty 6.1.11 fixes the problem. I tried adding "-Dorg.mortbay.util.URI.charset=utf-8" to my VM parameters with no luck. I intercepted the request with Fiddler2, and the correct bytes are encoded in the request. (Fiddler2 also identifies the post data as "Héy.")

Web page:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Submission to check encoding</title><meta content="text/html; Charset=utf-8" http-equiv="content-type" />
</head><body>
<form method="post" action="/www.einvite.com-6.0-SNAPSHOT/email/wording" id="theForm">
<textarea name="testText" id="group1" rows="3" cols="40">Héy.</textarea>
<input name="textSubmit" id="textSubmit" value="Submit Text" type="submit" />
</form>
</body>
</html>

Controller method: (Spring 2.5 gives the request object to the method):
@RequestMapping(value = "/texttest", method = RequestMethod.POST)
public String postTestText(final HttpServletRequest request)

{ final String testText = request.getParameter("testText"); System.out.println("Text text: " + testText); return "testText"; }

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. JETTY-633 Jetty's handling of ISO-8859-1 POST requests

  • Major - Major loss of function.
  • Resolved - A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jan Bartel added a comment -

JETTY-633 changed the default interpretation of the post contents encoding 8859_1 from UTF-8 in accordance with the HTTP spec:

http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7.1

Show
Jan Bartel added a comment - JETTY-633 changed the default interpretation of the post contents encoding 8859_1 from UTF-8 in accordance with the HTTP spec: http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7.1
Hide
Permalink
Jan Bartel added a comment -

This suggestion from the jetty lists shows you how to set the char encoding for the form data:

On Friday, January 9, 2009 at 12:28:27 AM, Simone Bordet wrote:
.
> > I think most (if not all) modern browsers encode form data using the
> > charset of the page they received, so if you specify the charset in
> > the form page, you know which charset to set in the request on server
> > side.

The only certain way of getting the encoding you want from all browsers is to use <form ... accept-charset='UTF-8'> </form>

Chris

Show
Jan Bartel added a comment - This suggestion from the jetty lists shows you how to set the char encoding for the form data: On Friday, January 9, 2009 at 12:28:27 AM, Simone Bordet wrote: . > > I think most (if not all) modern browsers encode form data using the > > charset of the page they received, so if you specify the charset in > > the form page, you know which charset to set in the request on server > > side. The only certain way of getting the encoding you want from all browsers is to use <form ... accept-charset='UTF-8'> </form> Chris
Hide
Permalink
Jan Bartel added a comment -

Hi Adam,

I'm closing this issue because it isn't a bug in jetty. We just changed the default charset encoding in accordance with the HTTP spec.

If you're still having problems with getting the browser to generate the correct charset encoding, then please continue posting to the jetty user@jetty.codehaus.org list and the folks there will do their best to point you in the right direction.

cheers
Jan

Show
Jan Bartel added a comment - Hi Adam, I'm closing this issue because it isn't a bug in jetty. We just changed the default charset encoding in accordance with the HTTP spec. If you're still having problems with getting the browser to generate the correct charset encoding, then please continue posting to the jetty user@jetty.codehaus.org list and the folks there will do their best to point you in the right direction. cheers Jan

People

  • Assignee:
    Unassigned
    Reporter:
    Adam Augusta
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: