[jira] [Resolved] (COMPRESS-316) CompressorStreamFactory doesn't handle deflate streams with a zlib header

["Stefan Bodewig (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/COMPRESS-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Bodewig resolved COMPRESS-316.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.10

patch committed with svn revision 1681356

My reading of RFC1950 is that the second byte could also have four different values when using preset dictionaries, but then we might be getting too many false positives.

Thanks!

> CompressorStreamFactory doesn't handle deflate streams with a zlib header
> -------------------------------------------------------------------------
>
>                 Key: COMPRESS-316
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-316
>             Project: Commons Compress
>          Issue Type: Bug
>          Components: Compressors
>    Affects Versions: 1.9
>            Reporter: Nick Burch
>             Fix For: 1.10
>
>         Attachments: zlib-header-detection.patch
>
>
> If you take a zlib / deflate compressed file, with the zlib header (eg the test file bla.tar.deflatez) and pass it to CompressorStreamFactory.createCompressorInputStream, it won't be detected and you'll get a CompressorException("No Compressor found for the stream signature.")
> While detecting header-less zlib files is probably too tricky to manage, those with the header ought to be possible to spot and handle



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)