Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-6798

applySafeRedirector (e.g. on Hudson restarting page) reloads on 502 responses

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Fixed but Unreleased (View Workflow)
    • Priority: Trivial
    • Resolution: Fixed
    • Component/s: core
    • Labels:
      None
    • Environment:
      Windows Vista SP2 64bit, Java 1.6.0_20 64bit, running as Windows service
    • Similar Issues:
    • Released As:
      2.207

      Description

      When Jenkins is set up behind a reverse proxy (such as IIS, nginx, etc.), when restarting, the page reloads too early.

      This seems to boil down to the proxy HTTP error, 502, not being considered by applySafeRedirector() in hudson-behavior.js and loading.js

        Attachments

          Issue Links

            Activity

            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            Not an INFRA issue, reassigned to the core

            Show
            oleg_nenashev Oleg Nenashev added a comment - Not an INFRA issue, reassigned to the core
            Hide
            danielbeck Daniel Beck added a comment -

            Why is IIS sending HTTP 502 Bad Gateway, rather than 503 Service Unavailable? Seems like an IIS bug.

            Show
            danielbeck Daniel Beck added a comment - Why is IIS sending HTTP 502 Bad Gateway, rather than 503 Service Unavailable? Seems like an IIS bug.
            Hide
            twpol James Ross added a comment -

            503 Service Unavailable doesn't seem to fit because the server (IIS) is available and handling the request - it is upstream which is broken. Where as 502 Bad Gateway and 504 Gateway Timeout seem like the expected possible responses in this situation, depending on whether the proxy (IIS) could connect to upstream or not.

            In any case, it's a trivial fix which doesn't have a downside AFAIK so I just don't understand the point of your comment.

            Show
            twpol James Ross added a comment - 503 Service Unavailable doesn't seem to fit because the server (IIS) is available and handling the request - it is upstream which is broken. Where as 502 Bad Gateway and 504 Gateway Timeout seem like the expected possible responses in this situation, depending on whether the proxy (IIS) could connect to upstream or not. In any case, it's a trivial fix which doesn't have a downside AFAIK so I just don't understand the point of your comment.
            Hide
            olivergondza Oliver Gondža added a comment -

            Nginx behaves the same way: 502 while Jenkins does not respond.

            Show
            olivergondza Oliver Gondža added a comment - Nginx behaves the same way: 502 while Jenkins does not respond.
            Hide
            vlatombe Vincent Latombe added a comment -

            Also affects the new loading.js for the login screen.

            Show
            vlatombe Vincent Latombe added a comment - Also affects the new loading.js for the login screen.

              People

              Assignee:
              vlatombe Vincent Latombe
              Reporter:
              twpol James Ross
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: