I’m encountering an issue using a specific value (the string ‘tk’) as a URL path parameter in the first segment on my published domain. My setup works fine with other values, and ‘tk’ doesn’t cause any problems when it appears in the second segment of the URL. However, I need to use a path parameter at the beginning of my URL, but I’m concerned about the potential risk that other string values could trigger similar issues in the future. Could this be a bug?
I’ve already tried a few things: republishing the project, leaving default values empty, and using different default values. Nothing had an effect so far.
The URL works fine when navigating through WeWeb, but it fails when reloading the page or manually entering it into the browser’s address bar.
I suspect there may be some residue from early development when I had ‘tk’ hardcoded instead of using a dynamic parameter or something. But probably nothing I could resolve by myself.
·) Url path parameter as first segment
https://mydomain.com/tk/login → 404
https://mydomain.com/something_else/login → works fine
·) Url path parameter as second segment
https://mydomain.com/login/tk → works fine as second segment