My Sandbox Apps links to not found

Hello,

I have noticed at our site, if you have a sandbox passenger application, in the “My Sandbox Apps” if you click the launch button for the app you get get a not found. Batch connect apps, either developer or system launch correctly however.

I can manually navigate to /pun/dev/<appname> and that will work fine. I now have a fixed developer dashboard, after some fumbling with ChatGPT.

The leading theory is that the way the routes are setup, having a ‘.’ (period) is not allowed in usernames in a route. Which normally is not an issue because the username/owner is an optional parameter and seems to only be used when launching sandbox passenger apps.

Maybe this should have been a GitHub issue, but I wasn’t sure if anyone else has noticed this behavior before.

Aaron

Hi and welcome!

What’s the appname that’s giving you issues? If I create an app called foo.test I don’t even see it in the list of sandbox apps.

In any case - yea it sounds like a bug somewhere. I’ve never seen it myself, but am seeing odd things playing around with it.

Maybe - Rails will recognize the end of a URL with a dot as the format. I.e., /some/app/url.json is requesting the /some/app/url in JSON format.

You can see here how we turn this off for the file browser so that you can actually access JSON files (i.e., :format => false)

It’s not the appname I was referring too in this case but it likely suffers from the same issue.

The issue is when the launch button links you to this route it appends the username into the owner parameter in the route here.

I think you are right about the format getting picked up, so for example when the launch button links to /pun/sys/dashboard/apps/show/ood-example-flask-app/dev/aaron.m.janssen it’s really hitting .../ood-example-flask-app/dev/aaron.m with format = .janssen or maybe a little different because of the double period but you get the gist.

I guess it is also worth noting the the next line down in this file needs the same fix because some app’s icons are getting 404’s because of the same reason.

You can change the routes of you developer dashboard. Indeed, you can use your development dashboard to boot other development applications.

I’d suggest maybe making that patch to your development dashboard, then attempting to boot ood-example-flask-app from your development dashboard that has the patch.

It seems like you’re the first developer with a . in their name! At any rate - seems like an easy enough patch for us to make it if works.