P4
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
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
- duplicates
-
JDK-6272064 plugin cannot handle URLs with ascii substitution (walnut_grove -> walnut%5Fgrove)
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Resolved
-
-
-
- Resolved
-