-
Notifications
You must be signed in to change notification settings - Fork 690
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
internal/contour: ensure the http.Router filter is present #2734
Conversation
Ensure that the `http.Router` filter is present whenever we build a HTTP Connection Manager. The `Router` filter is responsible for actually forwarding HTTP requests, so omitting it leads to configurations that are syntactically valid but otherwise inoperable. This fixes projectcontour#2733. Signed-off-by: James Peach <jpeach@vmware.com>
Codecov Report
@@ Coverage Diff @@
## master #2734 +/- ##
==========================================
+ Coverage 76.98% 77.03% +0.05%
==========================================
Files 72 72
Lines 5709 5722 +13
==========================================
+ Hits 4395 4408 +13
Misses 1226 1226
Partials 88 88
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a small nit on the run-test-case.sh script.
Also, I think we should collapse the HTTPConnectionManagerBuilder into less pieces as a future change, but that's a different PR.
Yeh, I expect we will see more changes to this API, e.g. the |
…ntour#2734) Ensure that the `http.Router` filter is present whenever we build a HTTP Connection Manager. The `Router` filter is responsible for actually forwarding HTTP requests, so omitting it leads to configurations that are syntactically valid but otherwise inoperable. This fixes projectcontour#2733. Signed-off-by: James Peach <jpeach@vmware.com>
Ensure that the
http.Router
filter is present whenever we build aHTTP Connection Manager. The
Router
filter is responsible for actuallyforwarding HTTP requests, so omitting it leads to configurations that
are syntactically valid but otherwise inoperable.
This fixes #2733.
Signed-off-by: James Peach jpeach@vmware.com