fix: fix caddy v2.7.x runtime error: ResponseWriter doesn't implement… #7
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
|
@Chilledheart Can you test if this works? |
|
"5. PS This PR does not" this PR is not for fix that log issue |
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.
… http.Flusher
1. What does this change do, exactly?
fix caddy v2.7.x runtime error: ResponseWriter doesn't implement http.Flusher by using ResponseController introduced in golang v1.20
2. Please link to the relevant issues.
klzgrad/naiveproxy#575
caddyserver#107
3. Which documentation changes (if any) need to be made because of this PR?
None
4. Checklist
5. PS
This PR does not fix an issue that caused the forwardproxy to not work when turning on the LOG directive in Caddyfile klzgrad/naiveproxy#550 (comment)