URL.absoluteString crashes if baseURL starts with colon #1119
+29
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Recent regression from reverting to compatibility
URL
behaviors in #1113.URL.absoluteString
usesURLComponents
to build the string from the correct parts of the relative and base URLs. After allowingURL
to have an empty scheme for compatibility in #1113,URL.absoluteString
would crash if we used an empty scheme from the base URL. The crash occurs when we assigncomponents.scheme = ""
sinceURLComponents
does not consider an empty scheme valid.Since we are only using
URLComponents
to produce an absolute string, we can bypass the scheme validation with an internal function, since the scheme used for the URL'sabsoluteString
has already been validated by the baseURL
.