-
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
global rate limiting policy ignored when defined for a TLS virtual host at the vhost level #3409
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Comments
skriss
added a commit
to skriss/contour
that referenced
this issue
Feb 25, 2021
Fixes a bug where global rate limit policies were being ignored when defined at the virtual host level on secure vhosts. Fixes projectcontour#3409. Signed-off-by: Steve Kriss <krisss@vmware.com>
skriss
added a commit
to skriss/contour
that referenced
this issue
Feb 25, 2021
Fixes a bug where global rate limit policies were being ignored when defined at the virtual host level on secure vhosts. Fixes projectcontour#3409. Signed-off-by: Steve Kriss <krisss@vmware.com>
skriss
added a commit
to skriss/contour
that referenced
this issue
Feb 25, 2021
Fixes a bug where global rate limit policies were being ignored when defined at the virtual host level on secure vhosts. Fixes projectcontour#3409. Signed-off-by: Steve Kriss <krisss@vmware.com>
skriss
added a commit
to skriss/contour
that referenced
this issue
Feb 26, 2021
Fixes a bug where global rate limit policies were being ignored when defined at the virtual host level on secure vhosts. Fixes projectcontour#3409. Signed-off-by: Steve Kriss <krisss@vmware.com>
skriss
added a commit
that referenced
this issue
Feb 26, 2021
Fixes a bug where global rate limit policies were being ignored when defined at the virtual host level on secure vhosts. Fixes #3409. Signed-off-by: Steve Kriss <krisss@vmware.com>
skriss
added a commit
to skriss/contour
that referenced
this issue
Mar 1, 2021
…ectcontour#3410) Fixes a bug where global rate limit policies were being ignored when defined at the virtual host level on secure vhosts. Fixes projectcontour#3409. Signed-off-by: Steve Kriss <krisss@vmware.com>
skriss
added a commit
that referenced
this issue
Mar 1, 2021
* internal/xdscache: include global rate limits for secure vhosts (#3410) Fixes a bug where global rate limit policies were being ignored when defined at the virtual host level on secure vhosts. Fixes #3409. Signed-off-by: Steve Kriss <krisss@vmware.com> * cmd/contour: pass pointers to StatusAddressUpdater (#3412) Fixes an issue where non-pointers were being passed to the StatusAddressUpdater when the load balancer address changed, which was resulting in HTTPProxies/Ingresses not immediately getting updated with the new address. Fixes #3411. Signed-off-by: Steve Kriss <krisss@vmware.com> * examples: update Envoy to 1.17.1 (#3417) Signed-off-by: Steve Kriss <krisss@vmware.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What steps did you take and what happened:
contour.stevekriss.com
repeatedly, observe the rate limit not taking effectWhat did you expect to happen:
The rate limit should take effect.
Anything else you would like to add:
Global rate limit policies for non-TLS vhosts work fine. Also, global rate limit policies defined on individual routes for a TLS vhost work fine.
As such, a valid workaround is to define your global rate limit policy once for each route on your TLS vhost.
Environment:
The text was updated successfully, but these errors were encountered: