Uploaded image for project: 'Maven Changes Plugin'
  1. Maven Changes Plugin
  2. MCHANGES-237

The goal jira-report always results in HTTP 400 error when accessing https://*.jira.com

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 2.4
    • Fix Version/s: 2.7
    • Component/s: jira
    • Labels:
      None

      Description

      The http-client used by plugin, rejects one of the cookies from https://company.jira.com and the missing cookie is the culprit of the 400 error. Maven 2.2.1 used. See extract below:

      27.4.2011 9:52:50 org.apache.commons.httpclient.HttpMethodBase processResponseHeaders
      WARNING: Cookie rejected: "$Version=0; studio.crowd.tokenkey=; $Path=/; $Domain=.davinci.jira.com". Illegal domain attribute ".davinci.jira.com". Domain of origin: "davinci.jira.com"
      27.4.2011 9:52:50 org.apache.commons.httpclient.HttpMethodBase processResponseHeaders
      WARNING: Cookie rejected: "$Version=0; studio.crowd.tokenkey=M2peMiHnn4NggIbmyHpKEQ00; $Path=/; $Domain=.davinci.jira.com". Illegal domain attribute ".davinci.jira.com". Domain of origin: "davinci.jira.com"
      27.4.2011 9:52:51 org.apache.commons.httpclient.HttpMethodBase getResponseBody
      WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.

        Attachments

          Activity

            People

            • Assignee:
              bmargulies Benson Margulies
              Reporter:
              jgabriel Gabriel Peter
            • Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: