ansaurus

Question

Answer 1

+2 A:

contentType: "application/x-www-form-urlencoded; charset=iso-8859-1"

You can say you're sending a form submission as ISO-8859-1 in the header, but that doesn't mean you actually are. jQuery uses the standand JavaScript encodeURIComponent() method to encode Unicode strings into query-string bytes, and that always uses UTF-8.

In any case, the ‘charset’ parameter for the MIME type ‘application/x-www-form-urlencoded’ is highly non-standard. As an ‘x-’ type there is no official MIME registration for this type, but HTML 4.01 doesn't specify such a parameter and it would be very unusual for an ‘application/*’ type. Weblogic claims to detect this construct, for what it's worth.

So what you can do is either:

1: create the POST body form-urlencoded content yourself, hacking it into ISO-8859-1 format manually, using something like

function encodeLatin1URIComponent(str) {
    var bytes= '';
    for (var i= 0; i<str.length; i++)
        bytes+= str.charCodeAt(i)<256? str.charAt(i) : '?';
    return escape(bytes).split('+').join('%2B');
}

instead of encodeURIComponent().

2: lose the ‘charset’ and leave it submitting UTF-8 as normal, and make your servlet understand incoming UTF-8. This is generally best, but will mean mucking around with the servlet container config to make it choose the right encoding. For Weblogic this seems to mean using an <input-charset> element in weblogic.xml. And by then you're looking at moving your whole app to UTF-8. Which is by no means a bad thing (non-Unicode-capable websites are sooo 20-century!) but may well be a lot of work.

bobince 2009-03-18 14:55:10

Thanks bobince, I'll try convert the pages but it'll take some time. I've tried the js encodeURI() and it worked but I had to manually decode each field from the request server side. I've tried also to put the xhr in utf-8 with the pages still in iso-8859-1 and it seems to work. Really strange..

Marco Z 2009-03-18 15:27:02

Answer 2

A:

I'm getting a similar error with IE, whereby I set contentType: "application/json" in my Ajax call, and this is what gets sent on the wire by FF, but IE adds the "application/x-www-form-urlencoded", so that on the wire it looks like: contentType: "application/x-www-form-urlencoded; application/json"

I don't have any fancy characters, but this seems to break the server (I'm using Jersey).

I could fiddle with the server, but it seems wrong that IE is adding the extra contentType, I'd much prefer to fix that. Any ideas?

Thanks

2009-05-21 10:46:44

Answer 3

A:

Actually just solved that, I needed to do:

jQuery.ajaxSetup({ contentType: "application/json;charset=utf-8" });

Which overrides the behaviour of adding application/x-www-form-urlencoded to the content-type in IE.

2009-05-21 12:21:12

Answer 4

A:

Thanks a lot !!! You help me find a solution to a problem that make me waste several days without finding any clue !!

2009-06-19 09:03:54

Answer 5

A:

Hi People, I was having similar problems, working in a content comments system in our Spanish Portal. What finally solved my problem, after many hours of searching, instead of messing with jQuery charset, that seems to use utf-8 no matter what, it was to decode from utf-8 back to ISO-8859-1 in the PHP that processed the ajax POST. In PHP there is a built in function, utf8_decode(), so the first thing I do with the comments string is this: $comentario = utf8_decode($_POST['comentario']);

(and then I used nl2br() and htmlentities() PHP functions in order to prepare the text to be stored with html entities instead of special chars)

Good Luck & Peace all over! Seba

Sebastian Alberoni 2010-06-03 23:18:39

ansaurus

tags:

views:

answers:

Another JQuery encoding problem, on IE

related questions