fix: whitelist git protocol paths instead of blacklisting non-git paths#255
Merged
alecthomas merged 1 commit intomainfrom Apr 14, 2026
Merged
fix: whitelist git protocol paths instead of blacklisting non-git paths#255alecthomas merged 1 commit intomainfrom
alecthomas merged 1 commit intomainfrom
Conversation
Switch handleRequest() from a blacklist approach (check for known non-git paths, treat everything else as clone/fetch) to a whitelist approach (only route /info/refs and /git-upload-pack to clone/fetch handling, forward everything else to upstream). This prevents LFS and other non-git requests from being misclassified as clone operations. Fixes #254 Co-authored-by: Claude Code <noreply@anthropic.com>
alecthomas
force-pushed
the
aat/fix-git-request-classification
branch
from
529e4eb to
facb98e
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Switch handleRequest() from a blacklist approach (check for known
non-git paths, treat everything else as clone/fetch) to a whitelist
approach (only route /info/refs and /git-upload-pack to clone/fetch
handling, forward everything else to upstream).
This prevents LFS and other non-git requests from being misclassified
as clone operations.
Fixes #254
Co-authored-by: Claude Code noreply@anthropic.com