RFR: 8272702: Resolving URI relative path with no / may lead to incorrect toString [v3]

[KIRIYAMA Takuya]

> Consider an authority component without trailing "/" as a base URI. When resolving a relative path against this base URI, the resulting URI is a concatenated URI without "/".
> This behaviour should be fixed, which is rationalized by rfc3986#section-5.2.3.
> Could you review this fix?

KIRIYAMA Takuya has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains three commits:

 - 8272702: Resolving URI relative path with no / may lead to incorrect toString
 - 8272702: Resolving URI relative path with no / may lead to incorrect toString
 - 8272702: Resolving URI relative path with no / may lead to incorrect toString

-------------

Changes: https://git.openjdk.org/jdk/pull/8899/files
 Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=8899&range=02
  Stats: 31 lines in 2 files changed: 23 ins; 0 del; 8 mod
  Patch: https://git.openjdk.org/jdk/pull/8899.diff
  Fetch: git fetch https://git.openjdk.org/jdk pull/8899/head:pull/8899

PR: https://git.openjdk.org/jdk/pull/8899