Fix where redirecting URLs may not include schemes or hosts #24
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.
Section 7.1.2 in RFC-7231 defines a "Location:" header for specifying the destination URL,
it may not contain schemes or hosts as shown in the example ("Location: /People.html#tim").
https://www.rfc-editor.org/rfc/rfc7231
However in NSISdl current implementation, the Location header's content is passed to the
connect() method as-is, so the first part up to "/" is interpreted as the host name,
so it fails.
This patch makes it possible to regenerate the destination URL from the original one.