maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesse Glick (JIRA)" <>
Subject [jira] Commented: (MINDEXER-13) *.gz index not loadable using default LightweightHttpWagon
Date Fri, 25 Mar 2011 20:59:22 GMT


Jesse Glick commented on MINDEXER-13:

Some experimentation reveals that httpd 2.2.9 will set this header if {{AddEncoding x-gzip
.gz}} is specified in {{httpd.conf}}. That directive is not enabled by default, but it is
suggested in a commented-out block:

    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz

There is no indication in these comments (or the manual) that using the directive violates
any RFC, and it seems likely enough that some admin or another would have uncommented such
a directive at some point for some reason, without having any clue this might affect Maven
indices. The Indexer would do well to behave gracefully in this case.

Workaround (without full server admin access) seems to be to create {{.index/.htaccess}} with

RemoveEncoding .gz

> *.gz index not loadable using default LightweightHttpWagon
> ----------------------------------------------------------
>                 Key: MINDEXER-13
>                 URL:
>             Project: Maven Indexer
>          Issue Type: Bug
>    Affects Versions: 4.0.0
>         Environment: Ubuntu, JDK 6u24
>            Reporter: Jesse Glick
>         Attachments: MINDEXER.diff
> If you create a new-style index (without {{--legacy}}), publish on an HTTP server (Apache
2.2.9 in my case), and try to download the remote index from a client using the default {{LightweightHttpWagon}},
the download fails.
> The wagon upon seeing {{Content-Encoding: gzip}} automatically decompresses the index
and serves the raw data. {{IndexDataReader}} then passes this to {{GZIPInputStream}} which
chokes. (MINDEXER-12 then conceals the actual problem and makes it look like the indexer only
accepts the legacy format.)
> Have a patch which seems to work. Probably {{DownloadRemoteIndexerManagerTest}} needs
to be enhanced to check this case; I am not very familiar with Jetty so I have not tried this
> (Nexus sends {{Content-Type: application/x-compressed}} but no content encoding so the
problem is not visible when using a Nexus mirror.)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message