-
Notifications
You must be signed in to change notification settings - Fork 5.5k
rate-limit: make 429 response mapping configurable #4879
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 3 commits
44967f0
161ba4d
bd1201e
d6a69ba
104bc64
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -7,13 +7,16 @@ | |
|
|
||
| #include "envoy/access_log/access_log.h" | ||
| #include "envoy/event/dispatcher.h" | ||
| #include "envoy/grpc/status.h" | ||
| #include "envoy/http/codec.h" | ||
| #include "envoy/http/header_map.h" | ||
| #include "envoy/router/router.h" | ||
| #include "envoy/ssl/connection.h" | ||
| #include "envoy/tracing/http_tracer.h" | ||
| #include "envoy/upstream/upstream.h" | ||
|
|
||
| #include "absl/types/optional.h" | ||
|
|
||
| namespace Envoy { | ||
| namespace Http { | ||
|
|
||
|
|
@@ -221,9 +224,11 @@ class StreamDecoderFilterCallbacks : public virtual StreamFilterCallbacks { | |
| * type, or encoded in the grpc-message header. | ||
| * @param modify_headers supplies an optional callback function that can modify the | ||
| * response headers. | ||
| * @param grpc_status the gRPC status code to override the httpToGrpcStatus mapping with. | ||
| */ | ||
| virtual void sendLocalReply(Code response_code, const std::string& body_text, | ||
| std::function<void(HeaderMap& headers)> modify_headers) PURE; | ||
| std::function<void(HeaderMap& headers)> modify_headers, | ||
|
venilnoronha marked this conversation as resolved.
|
||
| const absl::optional<Grpc::Status::GrpcStatus> grpc_status) PURE; | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I have been thinking more and more about our changes to the filter API. Every time we change this API we are making every person that has written thirdparty filters update. I don't know if there are better solutions to make argument extension in these functions easier/less painful for consumers. I am curious what the rest of the @envoyproxy/maintainers thoughts are about this.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We are tracking this concern here: #3390. Right now we decided that we are OK with API changes so that we can continue to move relatively fast. This will likely not always be the case.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. #3390 is for this, I think now we are OK but need release notes for extension impacting API changes. |
||
|
|
||
| /** | ||
| * Called with 100-Continue headers to be encoded. | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.