JDK-6181108 : double encoded URL passed to ResponseCache
- Type: Bug
- Component: core-libs
- Sub-Component: java.net
- Affected Version: 5.0,5.0u1
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic,windows_xp
- CPU: unknown,x86
- Submitted: 2004-10-19
- Updated: 2010-04-03
- Resolved: 2004-12-02
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 6 |
|---|
6 betaFixed  |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
This is related to bug #6177527. Currently, when a HttpURLConnection is opened to a URL which contains space chars (or any other character that needs to be encoded), the URL is encoded twice before it is passed to the ResponseCache, (if a ResponseCache is set). Note, the correct URL is used in the request. It is only the URL passed to the cache that is incorrectly encoded. For example, a path component "/space test/" would first be converted to "/space%20test/" and then to "/space%2520test/". ###@###.### 10/19/04 10:38 GMT Test case is added as attachment. The test will succeed (assuming the server is running) but you will see that the ResponseCache is given the wrong URI. ###@###.### 10/19/04 13:38 GMT
Comments
|