You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2009/06/25 19:09:54 UTC

[jira] Issue Comment Edited: (WAGON-264) compressed tarball download problems

    [ http://jira.codehaus.org/browse/WAGON-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=179794#action_179794 ] 

John Casey edited comment on WAGON-264 at 6/25/09 12:09 PM:
------------------------------------------------------------

The following headers are set by default in the latest trunk revisions of the httpclient-driven wagon (this is the http wagon that will be used in Maven 2.2.0):

{code}
            method.addRequestHeader( "Cache-control", "no-cache" );
            method.addRequestHeader( "Cache-store", "no-store" );
            method.addRequestHeader( "Pragma", "no-cache" );
            method.addRequestHeader( "Expires", "0" );
            method.addRequestHeader( "Accept-Encoding", "gzip" );
{code}

To disable the Accept-Encoding header, you will have to disable all of these default headers, then re-add the ones you want to keep. As of the versions checked into trunk, you can do this by editing the settings.xml, like this:

{code:xml}
<server>
  <id>myrepo</id>
  <configuration>
    <httpConfiguration>
      <all>
        <useDefaultHeaders>false</useDefaultHeaders>
        <headers>
          <header>
            <name>Cache-control</name>
            <value>no-cache</value>
          </header>
          <header>
            <name>Cache-store</name>
            <value>no-store</value>
          </header>
          <header>
            <name>Pragma</name>
            <value>no-cache</value>
          </header>
          <header>
            <name>Expires</name>
            <value>0</value>
          </header>
        </headers>
      </all>
    </httpConfiguration>
  </configuration>
</server>
{code}

Note that the above configuration will work for wagons accessed through the WagonManager in maven-artifact-manager. If you're managing Wagon instances elsewhere, you may need to provide access to the new HttpConfiguration and HttpMethodConfiguration config classes in wagon-http-shared.

      was (Author: jdcasey):
    The following headers are set by default in the latest trunk revisions of the httpclient-driven wagon (this is the http wagon that will be used in Maven 2.2.0):

{code}
            method.addRequestHeader( "Cache-control", "no-cache" );
            method.addRequestHeader( "Cache-store", "no-store" );
            method.addRequestHeader( "Pragma", "no-cache" );
            method.addRequestHeader( "Expires", "0" );
            method.addRequestHeader( "Accept-Encoding", "gzip" );
{code}

To disable the Accept-Encoding header, you will have to disable all of these default headers, then re-add the ones you want to keep. As of the versions checked into trunk, you can do this by editing the settings.xml, like this:

{code:xml}
<server>
  <id>myrepo</id>
  <configuration>
    <httpConfiguration>
      <all>
        <useDefaultHeaders>false</useDefaultHeaders>
        <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 the above configuration will work for wagons accessed through the WagonManager in maven-artifact-manager. If you're managing Wagon instances elsewhere, you may need to provide access to the new HttpConfiguration and HttpMethodConfiguration config classes in wagon-http-shared.
  
> compressed tarball download problems
> ------------------------------------
>
>                 Key: WAGON-264
>                 URL: http://jira.codehaus.org/browse/WAGON-264
>             Project: Maven Wagon
>          Issue Type: Improvement
>          Components: wagon-http-lightweight
>    Affects Versions: 1.0-beta-2, 1.0-beta-3, 1.0-beta-4, 1.0-beta-5
>            Reporter: Lee Thompson
>            Assignee: John Casey
>             Fix For: 1.0-beta-6
>
>
> HTTP wagon will uncompress tarballs it downloads, sometimes badly.  Downloading openssl results in an unpressed download
> $ mvn -X wagon:download-single -Dwagon.fromFile=openssl-0.9.8k.tar.gz -Dwagon.url=http://www.openssl.org/source -Dwagon.toDir=./
> $ tar tzf openssl-0.9.8k.tar.gz 
> gzip: stdin: not in gzip format
> tar: Child returned status 1
> tar: Error exit delayed from previous errors
> $ tar tf openssl-0.9.8k.tar.gz | more
> openssl-0.9.8k/apps/
> openssl-0.9.8k/apps/app_rand.c
> Downloading expat results in a corrupted file
> mvn -X wagon:download-single -Dwagon.fromFile=expat-1.98.8.tar.gz -Dwagon.url=http://prdownloads.sourceforge.net/expat -Dwagon.toDir=./
> $ tar tf expat-1.98.8.tar.gz 
> tar: This does not look like a tar archive
> tar: Skipping to next header
> tar: Read 1943 bytes from expat-1.98.8.tar.gz
> tar: Error exit delayed from previous errors

-- 
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