> Please review this PR which improves validation of unmappable characters in > names in the `ZipFileSystem` and `ZipFileOutputStream` APIs. > > Currently, `ZipFileSystem::getPath` and `ZipFileOutputStream:putNextEntry` > both throw `IllegalArgumentException` when rejecting a path or entry name > which cannot be encoded with the given charset. > > This PR fixes `ZipFileSystem::getPath` to instead throw > `InvalidPathException` as specified. Similarly, > `ZipOutputStream::putNextEntry` is updated to throw `ZipException` a > specified. > > Related, `ZipOutputStream::putNextEntry` is updated to reject unmappable > ZipEntry comments in a similar fashion. > > This change effectively means that `ZipOutputStream` now encodes names and > comments twice, once in `putNextEntry` and second time in `writeCEN` when the > stream is closed. An alternative would be to capture the encoded byte arrays > in the `XEntry`, however this would increase retained heap memory for large > number of entries. > > During work on this PR, I noticed that ZipFS ZipCoder.toString and > ZipCoder.getBytes implementations differ from those in java.util.zip. This PR > aligns ZipFS with java.util.zip. > > New tests are added in the ZipFS and ZipFileOutputStream area to verify that > these APIs throw exceptions according to their specifications when faced with > unmappable characters.
Eirik Bjørsnøs has updated the pull request incrementally with one additional commit since the last revision: Focus this PR on the single issue JDK-8380452 ------------- Changes: - all: https://git.openjdk.org/jdk/pull/30319/files - new: https://git.openjdk.org/jdk/pull/30319/files/c55ff710..3adedb00 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=30319&range=06 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=30319&range=05-06 Stats: 121 lines in 4 files changed: 14 ins; 82 del; 25 mod Patch: https://git.openjdk.org/jdk/pull/30319.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/30319/head:pull/30319 PR: https://git.openjdk.org/jdk/pull/30319
