URL conflict bug

I think you are correct. I created a test app with the url of /test and it worked. As soon as I named it similar to my published folder it failed.

Published folder: /images
Test App: /imagestest

I suggest you raise an issue here: GitHub · Where software is built

My theory is it may be related to a recent patched CVE around the published folder.

Agreed. This is a bug/enhancement that could use an issue.

Long story:

We kinda have a fundamental issue with URL validation across features. It’s pretty manual right now and I have actually run into this very problem recently. We implemented some checks but they’re not extensive and pretty error prone. Hence the CVE.

We do too much manual route checking and should really fall back on ASP.NET endpoint APIs to handle all this. We implemented that for apps in v5 but haven’t rolled it out across the platform. It would solve a lot of these types of issues but is a big churn.

There are issues for general URL fixes but haven’t bubbled up in a release yet.

Thanks @Adam Driscoll

It’s less of an issue now I worked out what’s going on. I can work around it.

But I honestly spent a long time trying to figure out why this one App wouldn’t load. There’s no clues in the logs because the admin area shows it running, the API response shows it running, there’s nothing in the App logs because for all intents and purposes, the App is running - it’s just not accessible from the front end.

We have a bit of placeholder for this issue since it’s been a problem for a while. There are actually a lot of ways to cause internal API conflicts.

github.com/ironmansoftware/powershell-universal
I’ll get it moved into a milestone so we can get it resolved once and for all.