WebDAV MKCOL failed: 400 Bad Request - cc-switch
Quick fix
No verified fix is available; NAS suggests using PROPFIND to check whether the directory exists after an MKCOL 400.
Symptom
Section titled “Symptom”WebDAV MKCOL 失败: 400 Bad Request
(http://<nas-ip>:5005/<share>/)WebDAV MKCOL failed: 400 Bad Request (http://<nas-ip>:5005/<share>/)
#5621 reports that a Chinese NAS returns `400 Bad Request` when MKCOL is run on the root of an existing shared folder. cc-switch's step-by-step directory creation logic only sends `405`, `409`, and redirect responses to PROPFIND for verification, so this 400 stops the process directly. Uploads and downloads also pass through this logic first, so PUT/GET do not run.
#1990 and its comments report a `502 Bad Gateway` variant when accessing WebDAV through Tailscale, WireGuard, or a self-hosted relay. The post provides no confirmed root cause or solution, so it cannot establish that this has the same cause as the NAS 400. Both issues are currently open; the described change is only the fix proposed in #5621 and has not been confirmed as merged or successful.
The original post provides no verifiable fix. You can follow the fix proposed in #5621: treat an MKCOL `400 Bad Request` as an ambiguous response that requires PROPFIND to verify whether the directory exists.
If the symptom is `502 Bad Gateway`, the original post provides no verifiable troubleshooting steps. Keep and add network tunneling and WebDAV configuration details to the relevant source issue.
Affected Versions
Section titled “Affected Versions”Source Issues
Section titled “Source Issues”This page is distilled from 2 real issues
(No FAQ yet)
Related problems
Section titled “Related problems”This is an unofficial community wiki with no affiliation to the cc-switch authors or the project itself. Its content is compiled from the project's public GitHub issues. This site distributes no software.