-
Notifications
You must be signed in to change notification settings - Fork 437
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
Expose config for Envoy's local reply mapper #3466
Labels
Comments
Is this something coming soon? |
@blackjid we have a few request for it but I don't think it will come in the 1.9 release. |
Ok, thanks for keeping us in the loop.. |
Zendesk ticket #2109 has been linked to this issue. |
This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs. |
github-actions
bot
added
the
stale
Issues that are stale. These will not be prioritized without further engagement on the issue.
label
Jun 12, 2024
:( |
github-actions
bot
removed
the
stale
Issues that are stale. These will not be prioritized without further engagement on the issue.
label
Jun 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Is your feature request related to a problem? Please describe.
I'd like to customize the response code, headers, and body based on initial response code (e.g. 404). This is supported by envoy via the local reply mapper: https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_conn_man/local_reply
Describe the solution you'd like
Expose config for Envoy's local reply mapper
The text was updated successfully, but these errors were encountered: