Details

    • Type: Sub-task
    • Status: Will Not Implement
    • Priority: High
    • Resolution: Unresolved
    • Affects Version/s: 5.4.6
    • Fix Version/s: None
    • Component/s: Access Server
    • Labels:
      None

      Description

      This is still broken as of 5.4.6. It is the cause of https://www.jfrog.com/jira/projects/RTFACT/issues/RTFACT-14834

      What's happening:

      If Artifactory is configured to serve both HTTP and HTTPS (and forward HTTP to HTTPS), on startup Artifactory will pick the HTTP access server url, rather than than HTTPS access server url. This works fine until Artifactory tries to perform a backup or system export. At that point, Artifactory will fail because it gets status code 302 (redirect), but does not acknowledge the redirect and instead fails since it's expecting status code 200.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              jsexton James Sexton
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated: