caddyhttp: Fix panic when request missing ClientIPVarKey #6040
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
francislavoie
force-pushed
the
fix-healthcheck-panic
branch
from
14c3964 to
d2cb865
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reported in https://caddy.community/t/caddy-v2-health-check-with-php-fastcgi-not-working/22334
Health checks make a
Requestand try to log it withLoggableHTTPRequest. When trying to marshal it, we doGetVar(r.Context(), ClientIPVarKey).(string)which panics because we never set this var in context for health checks.Fix is just to type assert in a guard instead of blindly using the value. Good enough.