I didn’t login since yesterday, so that’s why it’s timed out I guess.
Last piece of information.
After the previous screenshot showing I’m logged out, I did login via Locode, then called it again, getting info that I’m logged in (on this: /api/Authenticate?callback=loadAuth&jsconfig=eccn via Chrome URL bar).
Then I went back to Locode and did the switch to ApiExplorer, showing that I’m logged out (due to the 404), then immediately got back to the tab with the /api/Authenticate, reload, still logged in.
Previously I had tried to put all my API’s behind an /api route. I followed some advice on some older forum posts, and added the above, in addition to this:
//// put all routes behind /api path
//public override RouteAttribute GetRouteAttributes(Type requestType)
// var routes = base.GetRouteAttributes(requestType);
// routes.Each(x => x.Path = "/api" + x.Path);
// return routes;
which you can see I removed again. Just forgot to remove the first one.
So: no bug in SS just in my code
About serving under a path*
To host my services behind a path, I’d just use the rewrite functionality in the web server instead (incoming and outgoing), as well as informing SS using HandlerFactoryPath in the code.
I can mention that (as mentioned in another post), the links inside /ui and /locode (for switching between them) are using /, which could be fixed like this I think (tested by modifying in the browser/debugger (in my head I classify this as something SS should fix)