Interface ZipDirectoryEntryImportHttpOptions

true to throw an ERR_AMBIGUOUS_ARCHIVE error when calling FileEntry#getData if the local file header of the entry disagrees with its central directory record in a way that could make other tools (e.g. streaming readers based on local file headers) interpret the entry differently. This detects mismatched filenames, general purpose bit flags (encryption, data descriptor and language encoding flags), compression methods, CRC-32 checksums and sizes. The extra fields are not compared because the zip specification allows them to differ.

This is the boolean form of ZipReaderOptions#strictness: true means "strict" and false means any value but "strict". When both options are set, the value passed to FileEntry#getData takes precedence over the value passed to the constructor of ZipReader, and strictness takes precedence over checkAmbiguity when both are set at the same level. false downgrades an inherited "strict" value to "balanced" and leaves an inherited "tolerant" value unchanged.

true to verify the authentication code of entries encrypted with AES. The verification detects encrypted data tampered or corrupted after the encryption.

true to verify the CRC-32 checksum of the entry against the value stored in the zip file. The verification is run on the decompressed data and covers the whole read pipeline. It also applies to entries encrypted with AES in AE-1 format. It is skipped for entries in AE-2 format because they store a zeroed CRC-32 value.

true to validate the local file header of the entry against its central directory record when calling FileEntry#getData, false to skip that validation. This is the entry-level half of ZipReaderOptions#checkAmbiguity, exposed on its own so it can be enabled without the archive-level checks and disabled without giving up the rest of ZipReaderOptions#strictness. It is the only way to validate the local file headers of a self-extracting archive, since GetEntriesOptions#checkAmbiguity rejects prepended data outright.

true compares the filename as well, like ZipReaderOptions#strictness set to "strict"; false compares nothing, like "tolerant". An explicit value takes precedence over the strictness default at every level.

true to throw an ERR_OVERLAPPING_ENTRY error when calling FileEntry#getData if the entry overlaps with another entry on which FileEntry#getData has already been called (with the option checkOverlappingEntry or checkOverlappingEntryOnly set to true).

true to throw an ERR_OVERLAPPING_ENTRY error when calling FileEntry#getData if the entry overlaps with another entry on which FileEntry#getData has already been called (with the option checkOverlappingEntry or checkOverlappingEntryOnly set to true) without trying to read the content of the entry.

true to check only if the password is valid.

true to throw an ERR_HTTP_RESOURCE_CHANGED error when the ETag, Last-Modified or total size headers returned by a range request differ from the ones returned by the first range request, i.e. when the resource has been modified while being read. Headers missing from the responses are ignored, note that Access-Control-Expose-Headers must include them when the resource is fetched cross-origin.

true to check the CRC-32 checksum of the entry.

true to use Range: bytes=-22 on the first request and cache the EOCD, make sure beforehand that the server supports a suffix range request.

The encoding of the comment of the entry.

true to extract the appended data into ZipReader#appendedData.

true to extract the prepended data into ZipReader#prependedData.

The encoding of the filename of the entry.

How strictly the filename of each entry should be validated. A rejected name throws an ERR_UNSAFE_FILENAME error carrying the offending name in its filename property.

• "strict": reject the names rejected by "balanced", plus the names that do not map cleanly to a file path, i.e. empty names and names containing a "." path component or an empty one (e.g. "a//b.txt").
• "balanced": reject names that would escape the directory they are extracted into, i.e. names containing a ".." path component, and absolute names, i.e. names starting with "/", with a drive letter (e.g. "C:/file.txt") or with two backslashes (UNC paths).
• "tolerant": never reject a name.

A backslash is never interpreted as a path separator: it is a valid filename character on UNIX systems, and it also occurs as the trail byte of legitimate double-byte filenames (e.g. CP932) decoded with another charset.

Names are validated, never rewritten, so the filename reported for an entry always matches its central directory record.

true to always use Range headers when fetching data.

The HTTP headers.

The maximum number of bytes tolerated after the zip structure before the archive is rejected. Defaults to 0 when GetEntriesOptions#strictness is "strict", 65535 when it is "balanced", and Infinity when it is "tolerant".

An explicit value takes precedence over the strictness default at every level, so it can loosen "strict" or reintroduce a rejection under "tolerant". It also bounds how far back the end of central directory record is searched for, so a value smaller than the amount of data actually appended surfaces an ERR_EOCDR_NOT_FOUND error when the record lies beyond the searched region and an ERR_AMBIGUOUS_ARCHIVE error otherwise.

The maximum size in bytes of the range requests sent to read the data of an entry. The data is read with as many range requests as necessary, each response body being streamed, so that the size of a request never depends on the size of the entry.

true to read the data as-is without decompressing it and without decrypting it.

The password used to decrypt the content of the entry.

true to prevent closing of WritableWriter#writable when calling FileEntry#getData.

true to prevent using HEAD HTTP request in order the get the size of the content. false to explicitly use HEAD, this is useful in case of CORS where Access-Control-Expose-Headers: Content-Range is not returned by the server.

Leaving it unset is not the same as setting it to false when HttpOptions#useRangeHeader or HttpOptions#forceRangeRequests is set: the size is then read from a ranged GET request instead, and only an explicit false restores the HEAD request.

The password used to encrypt the content of the entry (raw).

The AbortSignal instance used to cancel the decompression.

How tolerant the reader should be when the local file header of an entry disagrees with its central directory record. Any difference throws an ERR_AMBIGUOUS_ARCHIVE error.

• "strict": compare the filename, the general purpose bit flag, the compression method, the CRC-32 checksum and the sizes.
• "balanced": compare everything except the filename.
• "tolerant": compare nothing and trust the central directory record.

Every field except the filename is read from the local file header anyway, to locate the entry data, so the comparison "balanced" performs reads no additional bytes. Comparing the filename reads the filename bytes as well, which costs one extra read per entry whenever the local file header carries no extra field — the common case in practice. Use ZipReaderOptions#checkLocalDirectory to request or suppress the whole comparison explicitly.

true to transfer stream ownership to web workers.

true to use the native API CompressionStream/DecompressionStream to compress/decompress data.

When compressing, the native API is only used when level is undefined or equal to 6, see ZipWriterConstructorOptions#level.

true to use Range headers when fetching data from servers returning Accept-Ranges headers.

true to use web workers to compress/decompress data in non-blocking background processes.

true to rely XMLHttpRequest instead of fetch to fetch data.