-
Enhancement
-
Resolution: Duplicate
-
P5
-
None
-
1.2.0
-
generic
-
generic
Currently in both JDK1.1.x and JDK1.2, URLEncoder only has one method URLEncode.encode(String data) which encodes the data by using default charater encoding type set by system property "file.encoding". However there are cases a browser needs to handle more than one encoding types at same time, so supporting more forms of encode method is necessary.
Request to add encode(String data, String charEncType) method.
[above by original submitter]
Note that this supports the convention that's been pushed by Netscape:
http://people.netscape.com/ftang/paper/unicode11paper/t005.html
as well as the more recent (March 1998) approach presented at the IETF:
ftp://ietf.org/internet-drafts/draft-masinter-url-i18n-01.txt
Both require encoding into bytes, then URL-encoding.
NOTE that whatever solution is adopted should be mirrored in the
new java.net.URLDecoder class too.
david.brownell@Eng 1998-07-06
Request to add encode(String data, String charEncType) method.
[above by original submitter]
Note that this supports the convention that's been pushed by Netscape:
http://people.netscape.com/ftang/paper/unicode11paper/t005.html
as well as the more recent (March 1998) approach presented at the IETF:
ftp://ietf.org/internet-drafts/draft-masinter-url-i18n-01.txt
Both require encoding into bytes, then URL-encoding.
NOTE that whatever solution is adopted should be mirrored in the
new java.net.URLDecoder class too.
david.brownell@Eng 1998-07-06
- duplicates
-
JDK-4257115 URLEncoder and URLDecoder should support target character sets
- Resolved
- relates to
-
JDK-4041072 Character set issues not addressed with URL's
- Closed
-
JDK-4100320 URLEncoder.encode() incorrect on non-ASCII platforms
- Closed