[
https://issues.apache.org/jira/browse/COMPRESS-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15244300#comment-15244300
]
Stefan Bodewig commented on COMPRESS-351:
-----------------------------------------
The output you see is what Compress considers the entry's file name. It looks
as if there was some garbage inside the local file header that results in
bigger blob being considered the name. I'll try to find a way to verify the
name consists of printing characters or something like this.
Is it OK to ship the attached archive as a unit test with Compress?
> Defective .zip-archive produces problematic error message
> ---------------------------------------------------------
>
> Key: COMPRESS-351
> URL: https://issues.apache.org/jira/browse/COMPRESS-351
> Project: Commons Compress
> Issue Type: Bug
> Components: Archivers
> Affects Versions: 1.11
> Environment: Production
> Reporter: Sven Kustos
> Attachments: DefectiveZipFileCausingBeeps.ZIP
>
>
> A truncated .zip-File produces an java.io.EOFException conatining a hughe
> amount of byte[]-data in the error-message - leading to beeps and crippeling
> workload in an potential console-logger.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
