Trailing slash in URI path routing

dz7

I'm having a problem getting URI routing to work for an application set up to point to a subdirectory of a domain. (For example, I've entered /path/ as the URI path when routing the application to the site.) Now, the application loads as expected when I navigate to domain.com/path/, but I get a 404 Not Found (nginx) error when navigating to domain.com/path without the trailing slash.
When I edit the site configuration and enter /path as the URI route instead, the system adds the trailing slash automatically so I can't set up the application to listen at /path.
I could work around this by setting up another site at the root domain domain.com and setting up a direct rule within that site, but it's not ideal to make a one-off change that has to be maintained within an unrelated site/application.
Is Opalstack site routing working as intended? Is there any way to change this through the site configuration?
Thanks!

nick

dz7 I believe this is part of the way the system adds the subdirectory path via the location block to NGINX. You'd probably have to setup your own stack to customise it the way you want to.

dz7

nick Thanks so much for the fast response! Adding a redirect rule seems like the easier option, but I appreciate the suggestion.

part of the way the system adds the subdirectory path

I'm not sure if you're saying that's an inherent behavior that can't be changed, but is this something I could submit to Opalstack as a feature request/suggestion? While it's not a major issue, it seems unexpected that a path wouldn't work without the trailing slash.

nick

dz7 If you open a ticket we can investigate your specific setup more closely and maybe get you a clearer answer to the issue. I was responding generally to what you put forward.