Verify an entry downloaded from an archive

Download one eligible archive member by its indexed row, check access and compression refusals, and verify a local copy without changing the archive.

Last reviewed

Downloading one member creates a local copy of that member; it does not extract every item or alter the ZIP, ISO, or IMG stored in Dosya.

Archive entry download workflow: open Archive contents, select the indexed file row, use Download, and verify the saved bytes while allowing for local filename sanitization.
Archive entry download workflow: open Archive contents, select the indexed file row, use Download, and verify the saved bytes while allowing for local filename sanitization. Open full-size screenshot.

Before you start

  • You must be able to view the archive through its folder path. A view_only file or locked or hidden ancestor can block the entry request.
  • ZIP members using Store (method 0) or Deflate (method 8) are eligible. Password-protected members and unsupported compression methods cannot be downloaded through this viewer.
  • Use the entry path and uncompressed size to distinguish duplicate base names in different folders.

Steps

  1. In Files, open the archive and wait for Archive contents to appear.
  2. Expand the relevant folders or enter part of the name in Filter entries. Select the exact file row, not a folder row.
  3. Check the displayed path, cleaned display name, and size. A blocked row explains This entry is password-protected or Compressed with a method this viewer cannot open (method N).
  4. In the entry stage, choose Download. For a format without an inline renderer, use Download this file on the fallback card.
  5. Allow the browser to save the response. The download header uses the raw final path segment as its UTF-8 filename, so the browser or operating system may sanitize it differently from Dosya’s cleaned display name. Compare its byte size and contents with the selected member.

If the download is refused

That entry is a folder, not a file. means the numeric row now addresses a directory. Reopen the archive and choose a file. A 409 response identifies an encrypted entry, while a 415 response names unsupported compression. A 413 listing refusal means the archive directory exceeded its processing budget; download the whole archive and inspect it locally instead.

Archive requests identify members by their numeric directory index rather than accepting a pathname from the URL. Display names also lose control characters, bidi controls, and . or .. segments. The numeric index prevents a crafted path from selecting a different server-side member. Browser and operating-system filename rules control the local destination, so choose an isolated folder and continue to treat the bytes as untrusted.

Expected result

The browser saves the chosen member using the response filename derived from the archive’s raw final path segment; local filename sanitization can change what appears on disk. No folder or file is added to Dosya, and the stored archive and its version remain unchanged; delete the local copy through your operating system if it is no longer needed.

Was this helpful?

Loading helpfulness results…

Voting saves a necessary ballot cookie for up to 180 days so you can change your answer.

Questions and replies

Ask about the steps in this guide. Questions are reviewed before publication.

Keep account details, credentials and private files out of public questions. Use private support for those.

Loading questions…

    Sign in to your Dosya account to ask a question.

    Check the outcome before you retry

    Use these shared checks when a task needs a second look.