[
https://jira.codehaus.org/browse/WAGON-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=288564#comment-288564
]
Andreas Sewe commented on WAGON-299:
------------------------------------
IMHO and from my reading of RFC 2616
<http://tools.ietf.org/html/rfc2616#section-14.11>, this is the HTTP server's
fault, not Wagon's. {{Content-Encoding}} is meant to be stripped of by the
client. Thus, the HTTP server should be configured to not send
{{Content-Encoding: gzip}} headers.
> tgz artifacts ungzipped on download
> -----------------------------------
>
> Key: WAGON-299
> URL: https://jira.codehaus.org/browse/WAGON-299
> Project: Maven Wagon
> Issue Type: Bug
> Reporter: Steinar Bang
>
> If a tgz artifact (in our case DLLs and shared libs for different platforms,
> that accompany a JNI wrapper Java library), is dowloaded from a maven
> repository on an HTTP server that sets the HTTP header "content-encoding:
> gzip" on the download, the downloaded file will be ungzipped before storing
> it in the local maven repository, still with the extension .tgz, and
> dependency:unpack will fail when attempting to unpack the library.
> This has been an upgrade blocker and have stuck us on version 2.0.4, which is
> getting increasingly hard, so from our POV it's at least priority "Major".
> We first encountered this problem on 2.0.5, and I unintentionally verified
> today that it's present in 2.0.7.
> I'm guessing it is in maven itself rather than in the
> maven-dependency-plugin, which is where we see it, because the same version
> of the maven-dependency-plugin works on 2.0.4, and fails on later mavens.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
