Repository navigation
Reject non-POST requests on gRPC and gRPC-Web servers - #377
Merged
Merged
Conversation
Motivation: The gRPC protocol requires POST for all requests but the server accepted any HTTP method. Changes: - Return 405 with Allow: POST header for non-POST gRPC/gRPC-Web requests - Add HttpMethodValidationTest Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
vietj
force-pushed
the
reject-non-post-request-for-application-grpc
branch
from
October 6, 2026 20:41
ecd931c to
e670f1e
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.
Motivation:
The gRPC protocol requires POST for all requests but the server
accepted any HTTP method.
Changes:
Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com