-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
André Warnier wrote:
>
> The OP is talking about UTF-16, not UTF-8.
I understand. I was trying to contrast UTF-8 and UTF-16, apparently
unsuccessfully.
> What you are saying above about ASCII/UTF-8 is true, if one restricts
> oneself to stri
Replying to myself :
André Warnier wrote:
My own name, expressed in the
Unicode alphabet and encoded in UTF-8, occupies 6 bytes, not 7.
I meant "6 bytes, not 5", of course.
It rather weakens my argument when I mix-up my own byte counts...
--
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
André Warnier wrote:
Could you tell us *why* exactly you [are trying to use UTF-16]?
It is rather unusual, as it supposes that you expect all clients to
encode their requested URI's in UTF-16 prior to sending the r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
André Warnier wrote:
> Could you tell us *why* exactly you [are trying to use UTF-16]?
> It is rather unusual, as it supposes that you expect all clients to
> encode their requested URI's in UTF-16 prior to sending the request to
> Tomcat on th
Nayyer Kamran wrote:
Hello,
I am facing problem in accessing deployed modules once I configured connector's
URIEncoding to "UTF-16" in server.xml.
Hi.
Could you tell us *why* exactly you did set this attribute ?
It is rather unusual, as it supposes that you expect all clients to
encode t
Hello,
I am facing problem in accessing deployed modules once I configured connector's
URIEncoding to "UTF-16" in server.xml. The log is showing nothing unusual but
no web module is accessible and throwing http status 404.
Can you some one told me what is the reason? Do I need to modify
