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 Bug
    • Status: Closed Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: 2.4
    • Fix Version/s: 2.7
    • Component/s: jira
    • Labels:
      None
    • Number of attachments :
      1

      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.

        Activity

        Hide
        Gabriel Peter added a comment -

        Excerpt from pom.xml:
        <reporting>
        <plugins>
        <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-changes-plugin</artifactId>
        <version>2.4</version>
        <reportSets>
        <reportSet>
        <reports>
        <!-<report>changes-report</report>->
        <report>jira-report</report>
        </reports>
        </reportSet>
        </reportSets>
        <configuration>
        <issueManagementSystems>
        <issueManagementSystem>JIRA</issueManagementSystem>
        </issueManagementSystems>

        <jiraUser>***</jiraUser>
        <jiraPassword>***</jiraPassword>
        </configuration>
        </plugin>

        </plugins>
        </reporting>

        <issueManagement>
        <system>JIRA</system>
        <url>https://davinci.jira.com/browse/***</url>
        </issueManagement>

        Show
        Gabriel Peter added a comment - Excerpt from pom.xml: <reporting> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-changes-plugin</artifactId> <version>2.4</version> <reportSets> <reportSet> <reports> <!- <report>changes-report</report> -> <report>jira-report</report> </reports> </reportSet> </reportSets> <configuration> <issueManagementSystems> <issueManagementSystem>JIRA</issueManagementSystem> </issueManagementSystems> <jiraUser>***</jiraUser> <jiraPassword>***</jiraPassword> </configuration> </plugin> </plugins> </reporting> <issueManagement> <system>JIRA</system> <url> https://davinci.jira.com/browse/*** </url> </issueManagement>
        Hide
        Gabriel Peter added a comment - - edited

        Any workaround is welcome...

        Show
        Gabriel Peter added a comment - - edited Any workaround is welcome...
        Hide
        Leon Stein added a comment - - edited

        In our case the problem was that HttpClient was refusing to accept authentication cookie from Jira, as it was set on a domain starting with dot (.<company>.atlassian.net). Setting BROWSER_COMPATIBILITY cookie policy on HttpClient fixes the problem (see attached patch).

        Show
        Leon Stein added a comment - - edited In our case the problem was that HttpClient was refusing to accept authentication cookie from Jira, as it was set on a domain starting with dot (.<company>.atlassian.net). Setting BROWSER_COMPATIBILITY cookie policy on HttpClient fixes the problem (see attached patch).
        Hide
        Benson Margulies added a comment -

        r1328930 | bimargulies | 2012-04-22 14:42:02 -0400 (Sun, 22 Apr 2012) | 2 lines

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

        ------------------------------------------------------------------------

        Show
        Benson Margulies added a comment - r1328930 | bimargulies | 2012-04-22 14:42:02 -0400 (Sun, 22 Apr 2012) | 2 lines MCHANGES-237 : The goal jira-report always results in HTTP 400 error when accessing https://*.jira.com ------------------------------------------------------------------------

          People

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

            Dates

            • Created:
              Updated:
              Resolved: