maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Casey (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (WAGON-269) Allow configuration of httpclient to change cookie policy, other options
Date Tue, 09 Jun 2009 16:11:42 GMT

     [ http://jira.codehaus.org/browse/WAGON-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

John Casey closed WAGON-269.
----------------------------

      Assignee: John Casey
    Resolution: Fixed

Fine-grained control now looks like the following:

{code:xml}
<server>
  <id>myrepo</id>
  <configuration>
    <httpConfiguration>
      <all>
        <params>
          <http.protocol.cookie-policy>ignoreCookies</http.protocol.cookie-policy>
        </params>
        <useDefaultHeaders>false</useDefaultHeaders>
        <headers>
          <!-- turn off Accept-Encoding from default headers, then re-add the rest of the
default headers -->
          <Cache-control>no-cache</Cache-control>
          <Cache-store>no-store</Cache-store>
          <Pragma>no-cache</Pragma>
          <Expires>0</Expires>
        </headers>
      </all>
    </httpConfiguration>
  </configuration>
</server>
{code}

Note that you have four configuration sections: all, get, put, and head. These correspond
to the HTTP methods used by the http wagon, plus 'all', which supplies configuration for all
methods in use.

> Allow configuration of httpclient to change cookie policy, other options
> ------------------------------------------------------------------------
>
>                 Key: WAGON-269
>                 URL: http://jira.codehaus.org/browse/WAGON-269
>             Project: Maven Wagon
>          Issue Type: Improvement
>          Components: wagon-http
>    Affects Versions: 1.0-beta-5
>            Reporter: John Casey
>            Assignee: John Casey
>             Fix For: 1.0
>
>
> In some cases, using non-lightweight http wagon can result in WARNING messages about
cookies with an incorrect path. This can be a particular problem where internal rewrite modules
change the location of a servlet that expects to be at a different path than the one the browser
used to access it.
> httpclient configuration options need to be exposed for configuration from the settings.xml
in order to allow users to fix this. Simply ignoring cookies is probably not a great option,
since some sites do rely on session cookies to maintain authentication, etc. Additionally,
there is a wealth of configuration available for httpclient, and exposing a method for configuring
this wagon comprehensively should help us head off future concerns about one of the other
config options.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message