-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.1.0
-
Fix Version/s: 3.2.0
-
Component/s: Content Selectors
-
Labels:None
-
Story Points:1
-
Epic Link:
-
Sprint:Sprint 83
Suppose i have some content in a docker repository (this most likely applies to other formats, this just happens to be the format i was using), and I want to restrict access to that content, I need to create content selectors that match against paths of "/v2/blah". These paths are now secured as i expect.
Problem is, when trying to test these queries using the content selector preview, I am forced to omit the leading slash to get any results. We should be able to use the same path matching in both cases
- relates
-
NEXUS-16703 Content selectors based on negative regular expressions do not handle leading slashes in a consistent manner
-
- Closed
-