|
Quick Lists
|
|
Bug ID:
|
4146652
|
|
Votes
|
6
|
|
Synopsis
|
java.net.URLEncoder.java needs to support more forms of encode method
|
|
Category
|
java:classes_net
|
|
Reported Against
|
1.2beta4
|
|
Release Fixed
|
|
|
State
|
11-Closed, duplicate of 4257115,
request for enhancement
|
|
Priority:
|
5-Very Low
|
|
Related Bugs
|
4041072
,
4100320
,
4154966
,
4257115
|
|
Submit Date
|
08-JUN-1998
|
|
Description
|
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. customer .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.
xxxxx@xxxxx 1998-07-06
|
|
Work Around
|
N/A
|
|
Evaluation
|
xxxxx@xxxxx 2000-04-24
See eval for 4257115
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |