headers: Fix Caddyfile parsing for request_header with matchers
#4085
Conversation
This file contains 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
|
Would you be able to give me an idea of a roadmap for this PR to be merged and available to install from a Docker image just so I stick something in my diary to sort out my hacky workaround? |
|
If you want to use it now, you can make a custom build by building from this branch: There's instructions on https://hub.docker.com/_/caddy, see the "Adding custom Caddy modules" section (you don't need to add plugins with |
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.
Fixes #4084
The first token needs to be skipped with
h.Next(), otherwise the matcher token is read as the header field.