OpenListTeam / OpenListTeam/OpenList
[BUG] 天翼云盘个人云上传下载405
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24.7k
- Forks
- 2.3k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 36
Description
请确认以下事项
-
我已确认阅读并同意 AGPL-3.0 第15条 。
本程序不提供任何明示或暗示的担保,使用风险由您自行承担。 -
我已确认阅读并同意 AGPL-3.0 第16条 。
无论何种情况,版权持有人或其他分发者均不对使用本程序所造成的任何损失承担责任。 -
我确认我的描述清晰,语法礼貌,能帮助开发者快速定位问题,并符合社区规则。
-
我已确认阅读了OpenList文档。
-
我已确认没有重复的问题或讨论。
-
我已确认是
OpenList的问题,而不是其他原因(例如 网络 ,依赖或操作)。 -
我认为此问题必须由
OpenList处理,而非第三方。 -
我已确认这个问题在最新版本中没有被修复。
-
我没有阅读这个清单,只是闭眼选中了所有的复选框,请关闭这个 Issue 。
OpenList 版本(必填)
v4.2.5
使用的存储驱动(必填)
天翼云盘
问题描述(必填)
天翼云盘个人云上传下载405
AI:OpenList v4.2.5 中,189CloudPC 驱动的 WebDAV 上传对个人云(type=personal) 会一直返回 405 Method Not Allowed,而对家庭云(type=family) 上传正常。
复现步骤:
- 部署 OpenList v4.2.5,挂载 189CloudPC 驱动的个人云(
type=personal)和家庭云(type=family),都用access_token登录方式。 - 通过 WebDAV 写入文件(任选其一):
- 命令行:
rclone copy test.txt openlist:tycloud/ - WebDAV 客户端(Windows 资源管理器拖入 / Cyberduck / RaiDrive 等)
- 命令行:
- 预期:文件成功上传到天翼云盘。
- 实际:返回
405 Method Not Allowed,文件未上传。 - 对比:家庭云(
openlist:family/)同样操作可成功上传。
已尝试的 workaround(均无效):
- 改
type为personal(原本是空)→ 仍 405 - 清空
family_id→ 仍 405 - 改
upload_method为stream/old→ 仍 405 - 删除并重建存储 → 仍 405
- rclone 直传 (
rclone copy) / curl 直接 PUT (curl -X PUT) → 都 405 - 切换
webdav_policy各种值 → 仍 405
预期行为:个人云和家庭云的 WebDAV 上传都应正常工作。
实际行为:仅家庭云(type=family)WebDAV 上传成功;个人云(type=personal)WebDAV 上传返回 405 Method Not Allowed,文件未上传到云端。
环境信息:
- OpenList 版本:v4.2.5(Commit: cc87e88,2026-08-07)
- 客户端:rclone v1.74.4 / curl / Windows 资源管理器
- 驱动:
189CloudPC - 操作系统:Windows 10/11
- 是否已确认是该版本特有:v4.2.4、v4.2.3 同样有此 bug
相关 issue(如已搜到):
- alist-org/alist #5182
[189CloudPC] WebDAV 无法备份/同步,状态码405 - alist-org/alist #832
189CloudPC WebDAV 无法上传百兆文件 - OpenListTeam/OpenList 暂未发现专门针对个人云/家庭云 WebDAV 写入差异的 issue
日志(必填)
2026/08/22 17:28:30 ERROR : bug_repro.txt: Failed to copy: unchunked simple update failed: Method Not Allowed: 405 Method Not Allowed
2026/08/22 17:28:30 ERROR : Attempt 1/3 failed with 1 errors and: unchunked simple update failed: Method Not Allowed: 405 Method Not Allowed
2026/08/22 17:28:31 ERROR : bug_repro.txt: Failed to copy: unchunked simple update failed: Method Not Allowed: 405 Method Not Allowed
2026/08/22 17:28:31 ERROR : Attempt 2/3 failed with 1 errors and: unchunked simple update failed: Method Not Allowed: 405 Method Not Allowed
2026/08/22 17:28:32 ERROR : bug_repro.txt: Failed to copy: unchunked simple update failed: Method Not Allowed: 405 Method Not Allowed
2026/08/22 17:28:32 ERROR : Attempt 3/3 failed with 1 errors and: unchunked simple update failed: Method Not Allowed: 405 Method Not Allowed
配置文件内容(必填)
{
"login_type": "token",
"username": "",
"password": "***REDACTED***",
"validate_code": "***REDACTED***",
"access_token": "***REDACTED***",
"refresh_token": "***REDACTED***",
"root_folder_id": "-11",
"order_by": "",
"order_direction": "",
"type": "personal",
"family_id": "***REDACTED***",
"upload_method": "stream",
"upload_thread": "3",
"family_transfer": false,
"rapid_upload": false,
"no_use_ocr": false,
"generate_torrent": false
}
复现链接(可选)
No response
AI生成内容(可选)
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the 405 with the 189CloudPC driver using a personal cloud mount, then compare its personal and family upload paths and configuration handling. Use the provided rclone, curl, or WebDAV client cases to verify the fix; done means personal-cloud uploads succeed without breaking family-cloud uploads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100