Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Issue #6473 - canonicalPath refactor & fix alias check in PathResource (Jetty-10) #6478
Issue #6473 - canonicalPath refactor & fix alias check in PathResource (Jetty-10) #6478
Changes from 3 commits
92a74d6
4cf9ca7
7b2d94b
37c657a
66b1cbb
9d98fe7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
This class was called
Ambiguous
so this is a breaking change.Also, why does it not implement
ComplianceViolation
, which seems to summarize the violation concept?On a closer look, I think this class here is a complete duplicate of
UriCompliance.Violation
.It's here because in 9.4.x we don't have
UriCompliance
(so it's a merge side-effect).Should it not be completely removed, so that in 10 we only use
UriCompliance.Violation
?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.
Ambiguous was public for a few releases, but not used in any interfaces at all, so I think it is OK to change.
But worth investigating if we can actually use UriCompliance.Violation here....
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.
See comment above, I think methods that expose
Violation
should be removed or changed to useUriCompliance.Violation
.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.
Fix indentation.
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.
See previous comment. This mapping from
HttpURI.Violation
toUriCompliance.Violation
should not be necessary.HttpURI
should just useUriCompliance.Violation
.