JDK-8213945 : Release Note: Changed URLPermission Behavior with Query or Fragments in URL String
- Type: Sub-task
- Component: core-libs
- Sub-Component: java.net
- Affected Version: 12
- Priority: P4
- Status: Closed
- Resolution: Delivered
- Submitted: 2018-11-15
- Updated: 2019-04-09
- Resolved: 2019-01-10
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 12 |
|---|
12Resolved  |
Description
The behavior of `java.net.URLPermission` has changed slightly. It was previously specified to ignore query and fragment components in the supplied URL string. However, this behavior was not implemented and any query or fragment were included in the internal permission URL string. The change here is to implement the behavior as specified. Internal usages of `URLPermission` in the JDK do not include queries or fragments. So, this will not change. In the unlikely event that user code was creating `URLPermission` objects explicitly, then the behavior change may be seen and that permission checks which failed erroneously previously, will now pass as expected.