Greetings,
On Wed, Jun 26, 2013 at 4:08 PM, Christopher Schultz < [email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > André, > > > > > But, even when sending UTF-8 encoded data according to this > > principle, they are *not* indicating that it is UTF-8 data, which > > is basically wrong, because the standard HTTP/HTML character set is > > iso-8859-1, and they *should* indicate it when that is not what > > they are sending. But that is the reality. > > No, as much as it pains me to do so, I agree with with Mozilla folks > on this one: adding a charset attribute to an > application/x-form-urlencoded Content-Type violates the spec. There is > no good solution. > ... > > > We really need an RFC for HTTP 2.0, with UTF-8 as the default > > charset/encoding. > > +1 > > Maybe they can clear-up Tomcat logging configuration while they are at > it :) > > Thank you! This discussion was quite informational. -Shanti
