check_http: Handle HTTPS & redirects when going through proxy #1862
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
What's the hold up with this? |
Member
|
Hi @jhonny-oliveira, |
|
Thank you for letting me know! I'm getting a feeling that I might be a bit outdated here. |
Member
|
If you are using |
|
I did not find a "Monitoring Plugins" in the RHEL/EPEL distro. I have reported this is issue in the right place now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
This is a fix for issue #1764.
The support in
check_httpfor "CHECK SSL WEBSERVER CONTENT VIA PROXY USING HTTP 1.1 CONNECT" is incomplete, in that it doesn't handle redirects.This patch makes it more complete, at least to the point where the following now works:
X.X.X.X:1234--onredirect=followis used