Details

    • Similar Issues:

      Attachments

        Activity

        Hide
        rtyler R. Tyler Croy added a comment -

        This is fixed in production

        Show
        rtyler R. Tyler Croy added a comment - This is fixed in production
        Hide
        mmccaskill Michael McCaskill added a comment -

        Olivier Vernin - Thanks for doing that. 

        Show
        mmccaskill Michael McCaskill added a comment - Olivier Vernin - Thanks for doing that. 
        Hide
        olblak Olivier Vernin added a comment -

        PR #828

        Show
        olblak Olivier Vernin added a comment - PR #828
        Hide
        olblak Olivier Vernin added a comment -

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

        Show
        olblak Olivier Vernin added a comment - Daniel Beck I really doubt that a plugin called 'API' has a representative name 
        Hide
        olblak Olivier Vernin added a comment -

        Indeed /api* is redirected to the backend.

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

        Show
        olblak Olivier Vernin added a comment - Indeed /api* is redirected to the backend. But Instead I can redirect /api/* to the backend
        Hide
        danielbeck Daniel Beck added a comment - - edited

        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

        Show
        danielbeck Daniel Beck added a comment - - edited 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
        Hide
        mmccaskill Michael McCaskill added a comment -

        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?

        Show
        mmccaskill Michael McCaskill added a comment - 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?
        Hide
        mmccaskill Michael McCaskill added a comment -

        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.

        Show
        mmccaskill Michael McCaskill added a comment - 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.

          People

          • Assignee:
            mmccaskill Michael McCaskill
            Reporter:
            danielbeck Daniel Beck
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: