if I make a public url of "Appname:AppView" and then I navigate to "www.domain.com/appname/app-view" it will redirect to authentication, but if I go to "www.domain.com/appname/app-view**/**" then it will bypass the authentication methodology.
The solutions we've found are
- Add it via public_paths
- Add in 2 public urls
- "Appname:AppView/"
- "Appname:AppView"
This isn't consistent since browsers, API calls, etc handle the appending of the "/" differently.
It would be good to make it so that it inherently handles both the forward slash'd version and non-forward slash'd version.