Uploaded image for project: 'Crucible'
  1. Crucible
  2. CRUC-3387

Wrong HTTP Links with AJP

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Handled by Support
    • Icon: Highest Highest
    • None
    • 2.2.1, 2.3.0
    • User interface

    • SLES 10, Apache 2.2, proxy_ajp_module

      Some links are broken, if Crucible is bounded via AJPv13 to Apache. The defect links contain an additional port number.

      My configuration is:
      <web-server context="crucible" site-url="https://hostname/">
      <ajp13 bind="localhost:8060" />
      </web-server>

      With this config can I access the Crucible user interface and make administrative settings. But if it comes to the point to create code reviews than point some buttons and links to http://hostname:8003/crucible/...

      Whereas I never configured port 8003.

      The "Create Review" button leads to an timeout. But a non-configured review is created.
      These reviews could not be accessed from the review list, because these links are broken too (http://hostname:8003/crucible/cru/CR-3).

      Also to mention is, that the Crucible reference from the Apache is set via https and the broken links using http.

            [CRUC-3387] Wrong HTTP Links with AJP

            Owen made changes -
            Workflow Original: FE-CRUC Bug Workflow [ 2938741 ] New: JAC Bug Workflow v3 [ 2955264 ]
            Owen made changes -
            Workflow Original: FECRU Development Workflow - Triage - Restricted [ 1512802 ] New: FE-CRUC Bug Workflow [ 2938741 ]
            Owen made changes -
            Workflow Original: FECRU Development Workflow - Triage [ 939824 ] New: FECRU Development Workflow - Triage - Restricted [ 1512802 ]
            Piotr Swiecicki made changes -
            Workflow Original: FECRU Development Workflow (Triage) [ 313495 ] New: FECRU Development Workflow - Triage [ 939824 ]
            Seb Ruiz (Inactive) made changes -
            Workflow Original: Simple review flow with triage [ 209643 ] New: FECRU Development Workflow (Triage) [ 313495 ]
            Seb Ruiz (Inactive) made changes -
            Resolution New: Handled by Support [ 8 ]
            Status Original: Needs Triage [ 10030 ] New: Closed [ 6 ]

            Seb Ruiz (Inactive) added a comment -

            If this is still affecting you, please raise a support request at http://support.atlassian.com. This JIRA instance is for our product development tracking; for a more prompt response in the future please raise a support issue

            Seb Ruiz (Inactive) added a comment - If this is still affecting you, please raise a support request at http://support.atlassian.com . This JIRA instance is for our product development tracking; for a more prompt response in the future please raise a support issue
            St. Wagner made changes -
            Affects Version/s New: 2.3.0 [ 15232 ]

            St. Wagner added a comment -

            Up-to-date version is now 2.3.0 and most links are fixed now, so we can use it (even if the release notes does not mention something about it). But links to user information are still broken.

            The Dashboard->Activity lists user activities. Each user is linked to /crucible/user/<username>. These links are still broken.
            Same situation on the Review board Reviews->Details->Participants. The href of the participants still contains the port number.

            St. Wagner added a comment - Up-to-date version is now 2.3.0 and most links are fixed now, so we can use it (even if the release notes does not mention something about it). But links to user information are still broken. The Dashboard->Activity lists user activities. Each user is linked to /crucible/user/<username>. These links are still broken. Same situation on the Review board Reviews->Details->Participants. The href of the participants still contains the port number.
            St. Wagner made changes -
            Priority Original: Major [ 3 ] New: Blocker [ 1 ]

              Unassigned Unassigned
              e64f6ae9b154 St. Wagner
              Affected customers:
              0 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: