-
-
Notifications
You must be signed in to change notification settings - Fork 675
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
fix: Explicitly setting http_tcp_listener.action_type to forward fails #281
Conversation
…listener.action_type-to-forward-fails
…listener.action_type-to-forward-fails
…listener.action_type-to-forward-fails
This PR has been automatically marked as stale because it has been open 30 days |
'Keep alive' comment |
It looks like this is going to help. Thanks @Jarodiv for |
@Jarodiv Thank you very much for this improvement! |
### [8.6.1](v8.6.0...v8.6.1) (2023-06-06) ### Bug Fixes * Explicitly setting http_tcp_listener.action_type to forward fails ([#281](#281)) ([b6cf424](b6cf424))
This PR is included in version 8.6.1 🎉 |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
Make the
http_tcp_listener
accept"forward"
as explicitly set value.Motivation and Context
If you need to set the value of
action_type
explicitly (e.g. to make redirecting optional), there is no working way to do so.This solves #280
Breaking Changes
There should be no negative effect on backwards compatibility with the current major version.
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request