Hi all,

I'm using Cocoon 2.1.8 w/ Jetty, and I'm having a problem with a character submitted in a form textarea. The user enters some text containing the '®' (registered sign) character. Mozilla LiveHTTPHeaders shows this on the wire as %C2%AE, which is the correct UTF-8 representation. However, the reply from the Cocoon app renders in the browser as '®', which I think is how it would look if the same byte sequence were interpreted as UTF-16 (or something :).

The request and reply headers look like this:

POST /dragonfly/12157e1661598c5a217151793a3e6421654c3614.continue HTTP/1.1
Host: fido.wd-2.net
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: https://fido.wd-2.net/dragonfly/article?issue-id=1&article-id=1
Authorization: Basic d2Q6Zmlkb2c=
Content-Type: application/x-www-form-urlencoded
Content-Length: 876
forms_submit_id=done&title=Visit+Our+New+Website&subTitle=&uri=http%3A%2F%2Fdragonflyadventures.com&category=Main&body=Mona+Treadway+and+Glenn+White%2C+Co-[...]

HTTP/1.x 200 OK
Date: Fri, 23 Jun 2006 15:42:13 GMT
Server: Jetty/4.2.23 (Mac OS X/10.3.9 ppc java/1.4.2_09)
X-Cocoon-Version: 2.1.8
Content-Type: text/html; charset=utf-8
Content-Length: 8024

Any ideas what might be going on here? Shouldn't there be a "charset" parameter in the POST Content-Type headers as well?

Thanks,
—ml—

Reply via email to