-
Notifications
You must be signed in to change notification settings - Fork 91
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
Implement RewriteHost #174
Implement RewriteHost #174
Conversation
The K-Network-Hash header will not match (or may not be present) if we redirect to an arbitrary host, so skip probing (which is best-effort anyway).
let me know if this would be easier to review with the two commits split in to different PRs |
/approve |
/assign @ZhiminXiang |
/lgtm /hold in case @ZhiminXiang has some comments |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: julz, tcnghia, ZhiminXiang The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
The following is the coverage report on the affected files.
|
Implementation of knative/serving#7748.
Note: it's not really sensible to try probing with a RewriteHost rule since we can't ensure the hash is what we expect, or even present (since it's returned by a different service), so this just skips probing if a RewriteHost rule is used.
Conformance test in serving: knative/serving#8592.
/assign @tcnghia @mattmoor