Ideally, while using the native browser, there is a possibility of the end user accessing the repository from the browser without the trailing slash “/” with the repository path.
Example:
[https://repositorylayout.jfrog.test/ui/native/repository-name]
If the concerned repository’s layout is incorrectly configured, then the resolution of the artifacts via the native browser would be impacted. Because, the artifacts expected to be listed in the destined location in correlation with the actual layout, would not match the path we are accessing, due to the conflict in the layout set at the repository level.
Example: For a maven repository, it is expected to have the Repository Layout set as “maven-2-default”, if the layout is incorrect and when trying to access the repository over a native browser without a trailing slash “/” at end, the error “Cannot construct a module info object from a blank item path” will be encountered.