[
https://issues.apache.org/jira/browse/COMPRESS-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15244579#comment-15244579
]
Sebb commented on COMPRESS-351:
-------------------------------
But the name may not be corrupted.
All we really know is that the archive is truncated.
If there are any other examples of Exceptions which include the file name these
would need to be 'protected' too.
So I'm still inclined to leave it to the app.
However if it is decided to keep the amended name, I would rather see the
message clarified to
"possibly corrupted name".
Or maybe keep the full name but replace non-printable chars with '?' as is done
by ls(1).
> 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
> Fix For: 1.12
>
> 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)
