When i did start this post, i had effectively a problem with the url encoding. But now i'm using the body of my request.
And i still have the issue. I followed the advice of Tristan, and know i use the setRequestHeader The problem is solved. In fact the problem is that with a java/servlet container as back end, normally the request is interpreted ISO-8859-1. Except if the request specify the charset that is used. So for java backend it is requiered to specify this. As i've seen, firefox add the charset in the content-type header. I don't know about internet explorer, and i can't test it. But for chrome, the content-type of the request doesn't include the charset if it is not explicitly add. 2011/7/12 Tristan Koch <[email protected]>: > Yes, you're right. It seems the special chars are transparently "url > encoded", so there is nothing to do on the JavaScript side. > > Still, I thinks its good to know that in the background an IRI is generated. > This means that the byte sequence of special characters are UTF-8 encoded. > Therefore, it should not be necessary to include a UTF-8 flag in the request > header. Put simply, its always UTF-8 and the backend knows which charset to > refer to for decoding. > > Am 12.07.2011 um 15:24 schrieb thron7: > >> >> >> On 07/12/2011 02:26 PM, Tristan Koch wrote: >>> Note the content type refers to the body of the request. Only requests send >>> with the methods POST or PUT include a body. If your URL includes special >>> characters, they should be encoded as byte sequence (to ensure they are >>> http safe, a subset of the ASCII character set). The mapping of byte >>> sequences to special characters is, I believe, defined in another standard >>> called IRI (and Punycode for the host name). >> >> Isn't that simply what is usually called "url encoding", you know "%20" >> for space and such (for the URL path), and is supported everywhere, also >> in Javascript?! >> >> T. >> >> >> >> ------------------------------------------------------------------------------ >> All of the data generated in your IT infrastructure is seriously valuable. >> Why? It contains a definitive record of application performance, security >> threats, fraudulent activity, and more. Splunk takes this data and makes >> sense of it. IT sense. And common sense. >> http://p.sf.net/sfu/splunk-d2d-c2 >> _______________________________________________ >> qooxdoo-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > -- Benjamin Dreux Analyste-Programmeur Chaire de logiciel libre-Finance Social et solidaire UQAM Montréal ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
