JDK-8147462 : URI.toURL could be more efficient for most non-opaque URIs
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.net
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2016-01-15
  • Updated: 2016-05-27
  • Resolved: 2016-01-29
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.
JDK 9
9 b104Fixed
Related Reports
Relates :  
JDK-8148626 - URI.toURL needs to use protocol Handler to parse file URIs
Description
For non-opaque URIs, the URI components will have been parsed and validated in accordance with the RFC2396 rules, but URI.toURL() goes the route via new URL(String spec) which validates the URI again. 

By going via one of URLs component based constructor, URI.toURL could be faster as well as allocate less garbage.