server: correctly route PATCH requests when using RouteHTTPToGRPC #347
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.
What this PR does:
Tempo relies on the
RouteHTTPToGRPC
option inserver
to handle HTTP and gRPC requests from a single endpoint. This options configures a multiplexer (soheilhy/cmux) to match and route HTTP and gRPC requests to their respective listener.For HTTP matching it uses
cmux.HTTP1Fast
which matches the method of the request with a predefined set of methods. This change addsPATCH
to the list to ensure PATCH requests are also sent to the HTTP listener.More details here: grafana/tempo#2756
For context, this configuration option was added a couple of months ago to support Tempo: weaveworks/common#288
Which issue(s) this PR fixes:
Fixes grafana/tempo#2756
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]