You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Stefan Bodewig (Created) (JIRA)" <ji...@apache.org> on 2012/03/23 14:35:26 UTC
[jira] [Created] (COMPRESS-184) PAX header parser fails for
non-ASCII values
PAX header parser fails for non-ASCII values
--------------------------------------------
Key: COMPRESS-184
URL: https://issues.apache.org/jira/browse/COMPRESS-184
Project: Commons Compress
Issue Type: Bug
Components: Archivers
Affects Versions: 1.3
Reporter: Stefan Bodewig
Assignee: Stefan Bodewig
Fix For: 1.4
The current logic parsing PAX extension headers fails if the number of bytes used to encode an entry is different from the number of characters - i.e. for any character outside of the ASCII range as the headers are UTF-8 encoded. E.g.
{noformat}
11 path=ä
{noformat}
takes 11 bytes (one has to account for the trailing newline) for 10 characters and the parser fails with "Expected 3 chars, read 2"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (COMPRESS-184) PAX header parser fails for
non-ASCII values
Posted by "Stefan Bodewig (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COMPRESS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Bodewig resolved COMPRESS-184.
-------------------------------------
Resolution: Fixed
fixed with svn revision 1304345
> PAX header parser fails for non-ASCII values
> --------------------------------------------
>
> Key: COMPRESS-184
> URL: https://issues.apache.org/jira/browse/COMPRESS-184
> Project: Commons Compress
> Issue Type: Bug
> Components: Archivers
> Affects Versions: 1.3
> Reporter: Stefan Bodewig
> Assignee: Stefan Bodewig
> Fix For: 1.4
>
>
> The current logic parsing PAX extension headers fails if the number of bytes used to encode an entry is different from the number of characters - i.e. for any character outside of the ASCII range as the headers are UTF-8 encoded. E.g.
> {noformat}
> 11 path=ä
> {noformat}
> takes 11 bytes (one has to account for the trailing newline) for 10 characters and the parser fails with "Expected 3 chars, read 2"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira