Wow this is weird. I can't reproduce locally but if I go to the plugin site and search for "API Fortress" I see it in the results. When I click it loads fine. But if I go directly to the link provided I get a 404, and not the nice 404 but the ugly Jetty one.

Upon further investigation it seems the 404 page is actually coming from Jetty, which means it's going to the API for some reason and not the React code. I'm assuming there's some routing issue, e.g. something that captures https://plugins.jenkins.io/<path> and is forcing /api* to go to the API. Olivier Vernin can you help me figure out if this is the case?

If that's the case, and it can't be limited to /api and /api/* specifically, should probably move to /_api to prevent this sort of problem.

On second thought, the above might be a good idea anyway – some day, the API plugin may show up

Indeed /api* is redirected to the backend.

But Instead I can redirect /api/* to the backend

Daniel Beck I really doubt that a plugin called 'API' has a representative name 

PR #828

Olivier Vernin - Thanks for doing that. 

This is fixed in production