Skip to content
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

Merged
merged 1 commit into from
Jul 27, 2020

Conversation

jpeach
Copy link
Contributor

@jpeach jpeach commented Jul 27, 2020

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 #2733.

Signed-off-by: James Peach jpeach@vmware.com

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>
@jpeach jpeach requested review from skriss and youngnick July 27, 2020 04:12
@codecov
Copy link

codecov bot commented Jul 27, 2020

Codecov Report

Merging #2734 into master will increase coverage by 0.05%.
The diff coverage is 83.33%.

Impacted file tree graph

@@            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              
Impacted Files Coverage Δ
internal/envoy/listener.go 97.08% <80.00%> (-0.66%) ⬇️
internal/contour/listener.go 94.87% <100.00%> (+0.93%) ⬆️
internal/featuretests/envoy.go 100.00% <100.00%> (ø)
cmd/contour/servecontext.go 93.44% <0.00%> (ø)
cmd/contour/serve.go 2.59% <0.00%> (+2.59%) ⬆️

_integration/testsuite/run-test-case.sh Show resolved Hide resolved
internal/envoy/listener.go Show resolved Hide resolved
Copy link
Member

@stevesloka stevesloka left a 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.

@jpeach
Copy link
Contributor Author

jpeach commented Jul 27, 2020

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 ext_authz filter needs to go in between the current list of default filters.

@jpeach jpeach merged commit 0886cd0 into projectcontour:master Jul 27, 2020
@jpeach jpeach deleted the fallback-default-filters branch July 27, 2020 21:53
tthebst pushed a commit to tthebst/contour that referenced this pull request Aug 6, 2020
…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Curl request hangs when SNI is omitted (httpproxy fallback certificate mode)
2 participants