JDK-6350321 : java.net.URI: the 'path' component should be present in opaque URIs
- Type: Bug
- Component: core-libs
- Sub-Component: java.net
- Affected Version: 6
- Priority: P2
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2005-11-15
- Updated: 2011-01-19
- Resolved: 2005-12-03
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 b63Fixed  |
Related Reports
|
Relates :
|
Description
the test
try {
URI u = new URI("host:opa:que?query#fragment");
System.out.println( u.getPath() );
} catch (URISyntaxException e) {
e.printStackTrace();
}
shows that this URI have null path. (parseServerAuthority has no effect:)
In this case path = 'opa:que'
RFC says that path can't be undefined, it can be empty
Comments
|