-
Notifications
You must be signed in to change notification settings - Fork 98
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
Prevent paths in HTTPRoute matches from conflicting with internal locations in NGINX #1445
Conversation
538b9d8
to
e64c291
Compare
LGTM on the docs side - since the changes in the PR are primarily code-based I will not make an approval. |
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.
thanks @salonichf5
this looks good. per review comment, let's update the prefix so that we don't need any restrictions on paths in HTTPRoute routing rules
internal/mode/static/nginx/config/validation/http_njs_match_test.go
Outdated
Show resolved
Hide resolved
b914fdd
to
7413fda
Compare
@salonichf5 can you update the PR description to reflect the new approach? |
@pleshakov Do you think with this change we still need the |
@sjberman |
Co-authored-by: Alan Dooley <[email protected]>
Co-authored-by: Michael Pleshakov <[email protected]>
7413fda
to
e6ff4eb
Compare
bac9dbb
to
84f47f0
Compare
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.
🚀
8d0be42
to
bba2edf
Compare
Proposed changes
Write a clear and concise description that helps reviewers understand the purpose and impact of your changes. Use the
following format:
Problem: To simplify routing, generated locations should be different from defined http route locations.
Solution:
internal
directive from server blockRewrite
&Redirect
for urlTesting:
curl request with version 2 header returns response from coffee-2
Please focus on (optional): If you any specific areas where you would like reviewers to focus their attention or provide
specific feedback, add them here.
Closes #428
Checklist
Before creating a PR, run through this checklist and mark each as complete.