• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • _unsorted
    • None
    • Platform: All, OS: Linux

      Currently, we have Apache proxying from /hudson to localhost:8080/hudson working
      just fine (vrsion 1.237). It doesn't append ?from= in the request string nor
      does it reply with an URL.

      However, it seems the new login script (version 1.251) insists on replying with
      an incorrect URL which screws up redirection after login. In my case, the
      replied URL was $HOST_NAME, instead of $HOST_NAME/hudson.

          [JENKINS-2275] Hudson login?from=

          Can you explain the steps to reproduce the problem better? What pages do you go,
          what links do you click, and where are you taken (which I suppose eventually end
          in 404)?

          Is this the same as issue #2290?

          Kohsuke Kawaguchi added a comment - Can you explain the steps to reproduce the problem better? What pages do you go, what links do you click, and where are you taken (which I suppose eventually end in 404)? Is this the same as issue #2290?

          Got an offline response from the submitter:

          My environment is not the same as issue 2290 because I'm making Hudson
          handle LDAP with matrix-based security, not using the container to handle
          security.

          My Apache has the following proxy passes

          1. Tomcat proxy
            ProxyPass /hudson ajp://localhost:8009/hudson
            ProxyPassReverse /hudson ajp://localhost:8009/hudson

          while the local tomcat is serving Hudson at /hudson.

          Since I don't allow anonymous access, if you go to https://<Apache>/hudson:
          1) for v1.242, you'd be redirected to https://<Apache>/hudson/login which
          works fine.
          or
          2) for v1.251, you'd be redirected to https://<Apache>/login?from=%2Fhudson%2F
          which doesn't exist.

          I believe this is the same as 2290, and as such fixed in 1.252.

              • This issue has been marked as a duplicate of 2290 ***

          Kohsuke Kawaguchi added a comment - Got an offline response from the submitter: My environment is not the same as issue 2290 because I'm making Hudson handle LDAP with matrix-based security, not using the container to handle security. My Apache has the following proxy passes Tomcat proxy ProxyPass /hudson ajp://localhost:8009/hudson ProxyPassReverse /hudson ajp://localhost:8009/hudson while the local tomcat is serving Hudson at /hudson. Since I don't allow anonymous access, if you go to https://<Apache>/hudson: 1) for v1.242, you'd be redirected to https://<Apache>/hudson/login which works fine. or 2) for v1.251, you'd be redirected to https://<Apache>/login?from=%2Fhudson%2F which doesn't exist. I believe this is the same as 2290, and as such fixed in 1.252. This issue has been marked as a duplicate of 2290 ***

            Unassigned Unassigned
            alvin_chang alvin_chang
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: