check_curl: fix relative redirects on non-standard port #2010
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.
Having a webserver respond with a relative redirect as for ex. in
Location: /path/to.htmlcheck_curl would use the wrong standard http/https port instead of crafting the absolute url using the given scheme/hostname and port.Adding a new test case for this for check_http and check_curl. check_http did it correct already, so no fix necessary there.
before:
Port 80 is wrong here.
fixed:
Correctly using the given port to craft the new url.