[zhoubiao188]

When ZipContent is opened for a nested directory (Kind.NESTED_DIRECTORY), entry names are virtualized: the name stored in the central directory record includes the directory name, while getName() strips it using nameOffsetLookups. hasNameStartingWith reads the record directly but doesn't strip the same offset, so it compares the prefix with the complete name.

For a nested directory d/ containing 9.dat, getName() returns 9.dat, but hasNameStartingWith("9.dat") returns false until getName() happens to have been called:

try (ZipContent zip = ZipContent.open(path, "d/")) {
    Entry entry = zip.getEntry(0);
    entry.hasNameStartingWith("9.dat");   // false
    entry.getName();                      // "9.dat"
    entry.hasNameStartingWith("9.dat");   // true (name is now cached)
}

This contradicts the method's own contract and makes the result depend on call order. It also prevents MetaInfVersionsInfo from seeing versioned entries in nested directory content, because it relies on hasNameStartingWith("META-INF/versions/").

Fix

Apply the same nameOffsetLookups offset that getName() uses. A regression test is included.

[wilkinsona]

Thanks again, @zhoubiao188.