ManYue: Check WebDAV filenames separately from encoded URI components

Seeing a server entry does not establish that a manually assembled link identifies it. Spaces, hashes and percent signs have encoding boundaries. Check one authorized known sample without changing real server settings, recording normal ManYue browsing separately from trusted external link inspection rather than adding characters repeatedly to diagnose every failure.

Fix server and sample identity

Choose an existing authorized WebDAV folder and known small comic. Record server alias, directory hierarchy, full name, size and content anchor without publishing credentials. The teaching filename chapter 1#draft.cbz contains literal space and hash; no server creation or overwrite is required. Without such a sample, record ordinary identity and special characters untested. Confirm the same account and visible folder through normal browsing. Authentication, permission and unavailable-directory failures remain separate from encoding.

Separate directory names from URI representation

Record the literal filename separately from an actual link supplied by a trusted server or client, retaining sensitive hosts and tokens privately. A display name is not already an encoded URL, and a browser’s prettified address is not the raw link. Without authorized access to a link, record browsing/reading only. Path, query and fragment are distinct URI components; do not append a filename question mark or hash as a new query or fragment. Preserve the original before interpretation.

Interpret encoding within one name component

Under URI rules, the sample path component can be chapter%201%23draft.cbz: space becomes %20 and the filename hash %23. A raw URI hash introduces a fragment, so draft no longer belongs to that filename path. This ASCII example does not teach guessing byte encodings for non-ASCII names; prefer trusted client-generated links. Structural slashes remain separators. Do not encode an entire address as one filename or insert credentials and tokens into the example.

Do not blindly encode existing percent triplets again

Reprocessing an already encoded %20 may produce %2520, a different layer representing literal percent-two-zero. A filename actually containing percent may correctly need %25. Compare original name and supplied link rather than repeatedly decoding until it looks familiar. Plus can represent space in some form-query conventions, not every path plus. Preserve component and provenance. If unfamiliar with encoding, do not change a working connection or save a guess as the global server address.

Verify normal browsing and external links separately

Select the known entry normally in ManYue and check chapter, target content and final page without assuming a raw-URL inspector. If a trusted external tool can access the supplied link under the same permissions, record result and content identity separately, not merely success or a cover. A link may be a browser page, temporary signature or download route, so failure does not establish damage. Compare title, size or content anchors to exclude an old namesake. Do not give credentials to an unfamiliar website or alter server files.

Narrow the issue through comparison results

If ordinary names work but special names fail, record character, path and entry rather than declaring the whole server unavailable. If both fail, inspect network, authentication, permission and response content. A single observation without a control cannot prove encoding causality. Preserve differences between supplied and hand-built links without treating the latter as authoritative. Restrict reversible configuration tests to familiar copies, retaining the working connection. Encoding changes neither bypass access controls nor repair permissions.

Preserve structure while sanitizing a report

Use a sample domain and invented name preserving space/hash/percent structure, with app version, entry and visible message. Do not publish tokens, passwords, private titles or live library links. Recheck sanitization so converting %23 to a raw hash does not destroy the issue, and do not substitute unrelated names while claiming identical steps. Share necessary log fragments with originals privately retained, without inventing requests performed. A short directory-to-page path is more useful than credential-bearing logs.

Confirm the same file after returning

Leave the reader and return through the original directory, checking name, content and resumed position. Retain literal name and URI representation, permission environment, actual results and unresolved causes. Restore any copied-configuration test and confirm the original directory remains accessible. Completion identifies file, component and access path, not a claim that knowing %20 fixes every special-character issue or that external success verifies every ManYue download and offline step.

Related guides and sources

Connect ManYue to WebDAV: check the address, library and downloads; ManYue HTTPS and proxy subpaths: what to check after a browser opens.

Checked on November 9, 2026: Apple public version information lists ManYue 2.0.4, requiring iOS / iPadOS 15.0 or later. Feature scope follows the official App Store description and the installed version. This article provides reading and checking methods you can perform; it does not claim step-by-step physical-device or private-server testing. Manual records, external tools and actually visible controls are identified separately, and personal analysis or code observations are not presented as verified automatic capabilities.

For the concept or external-tool scope, see RFC 3986: URI Generic Syntax. Samples, checking sequences and observation records here are original reading exercises. External references establish no new automatic recognition, editing or inference in the app and do not replace checking the actual file or passage.