-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Adam,
Adam Gordon wrote: > After some digging, there's URIEncoding attribute on the Connector > element that if not specified defaults to ISO-8859-1 when attempting to > decode URI bytes. I suspect setting this to UTF-8, in addition to the > other changes we made (the @page directive and <meta> tag directive for > the Content-Type, and the acceptCharset attribute on html:form all to > UTF-8) will fix the problem...we'll see. Unless you posted inaccurate information in the past, this is not the problem. The URIEncoding attribute only sets the character encoding for the URI submitted in the HTTP method line (i.e. "GET /foo/bar/baz" or "POST /foo/bar/baz"). Since you said you were using POST, there should be no form data in the method portion of the request. The body of an HTTP request ought to be interpreted using the Content-Type header provided with the request. The interpretation of the request body will not change regardless of the URIEncoding attribute value. > After reading some of the developer comments in the filed bugs, UTF-8 > appears to be the only standard on URL encoding, however according to > them in 2003, no one really paid attention it - hopefully this is not > the case anymore. If you want to accept non-latin1 characters, you should set /everything/ to UTF-8. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGYGN79CaO5/Lv0PARAmOmAJ48hwaT5BDW5/BkNNNvYmLQUNFl/QCfUnTL dUiSuB1P+mTbfrcuhca1CIA= =3/Ir -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
