On 2/1/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: The form that gets sent to the browser is in UTF8, and the browser
: correctly sends back UTF8 in the post body. *But* the browser doesn't
: tell the container what the charset of the body is, so it's up to the
: container to guess. By default, resin seems to pick latin-1.
That's really weird ... i could have sworn browsers doing POST of form
data were suppose to sent a full content-type...
Content-type: application/x-www-form-urlencoded; charset=utf-8
...picking the charset based on the charset of the page containing the
form (i assume you tested and verified this isn't happening?)
Yep, FireFox2.
I'd serve the page, do a search, kill the solr server, run nc -l -p
8983, and run the search again. The body was encoded correctly, but
just no charset info.
I tried setting it explicitly by appending to enctype in the form, but
it doesn't go through.
-Yonik
