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

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

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Trivial
    • Resolution: Fixed
    • core
    • None
    • Windows Vista SP2 64bit, Java 1.6.0_20 64bit, running as Windows service
    • 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

          links to

          Web Link PR #4366

          Activity

            Ascending order - Click to sort in descending order
            oleg_nenashev Oleg Nenashev added a comment -

            Not an INFRA issue, reassigned to the core

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

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

            danielbeck Daniel Beck added a comment - Why is IIS sending HTTP 502 Bad Gateway, rather than 503 Service Unavailable? Seems like an IIS bug.
            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.

            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.
            olivergondza Oliver Gondža added a comment -

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

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

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

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

            People

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

              Dates

                Created:
                Updated:
                Resolved: