- sets at lest in the javax.server.* interfaces. + sets at least in the javax.servlet.* interfaces.
And maybe it should be s/ISO?8859/ISO-8859/gi on all the docs? And, I'm starting to feel myself a provocateur s/UTF8/UTF-8/g (if it is not a function name) just for the reason of Name: UTF-8 [RFC2279] MIBenum: 106 Source: RFC 2279 Alias: None in the IANA registry? <DISCLAIMER> The cases of ISO 8859-1 and UTF8 maybe should be discussed separately. At least for the reason of UTF8 being often met in the *.c sources and cause JAVA runtime also recognizes UTF8 :) We just must be sure that no one has a slightest idea of sending UTF8 instead of UTF-8 in a Content-Type header! </DISCLAIMER> - Anton
