You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by bu...@apache.org on 2003/04/07 09:11:46 UTC
DO NOT REPLY [Bug 18752] New: -
the method to change the field values of HttpConstants
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18752>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18752
the method to change the field values of HttpConstants
Summary: the method to change the field values of HttpConstants
Product: Commons
Version: 2.0 Alpha 3
Platform: All
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Other
Component: HttpClient
AssignedTo: commons-httpclient-dev@jakarta.apache.org
ReportedBy: shinobo@leo.bekkoame.ne.jp
HttpContants has two fields , DEFAULT_CONTENTS_CHARSET and HTTP_ELEMENT_CHARSET.
These values are fixed to ISO-8859-1 and US-ASCII.
But it's more convinent,if can be altered.
For example, in japan,many sites use SJIS characters without enconding
declaration. and such environment, httpclient is hard to use when you must
handle external script files or style sheets which includes SJIS characters.
script files are sent withonut encoding declaration.
As you know some japanese SJIS kanji character has '\' in second byte.
if you assume that the enconding is ISO-8859-1, such character 'eats' next
character and make serious syntax errors in script evaluation.
IE or Mozilla are using technique that at first test contents character
enconding, and if coud'nt tell which enconding then use preffered enconding
SJIS,EUC-JP or others.
But for some applications, it's simply enough to assume default enconding is
SJIS or EUC-JP or other.