OpenListTeam / OpenListTeam/OpenList

[BUG] 115网盘对于部分文件一直报错请求失败 (405): Not Allowed

Open
#2,078 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
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.1.9

使用的存储驱动(必填)

115开放平台

问题描述(必填)

我在用openlist从一个存储复制到另一个存储的时候。 有个文件一直上传不了,甚至打开网盘的网页手动下载再上传也会失败(这是再网盘网页端手动上下载时的错误提示,openlist中操作报错的message为空,手动操作的报错报错:904 - HanuMankind - Go To Sleep(Explicit).flac 19.68 MB添加: 20:55:06失败: 20:55:06- 请求失败 (405): Not Allowed),我把双括号改成-就行了,如下904 - HanuMankind - Go To Sleep-Explicit.flac
可是文件789 - Mor W.A - Vademecum(Explicit)却毫无阻碍直接传过去了,这是为什么?难道是文件名中的特定字符组合触发了存储服务或 API 网关的 WAF(Web 应用防火墙)拦截?

日志(必填)

==============================================================================

POST  /open/upload/init  HTTP/1.1
HOST   : proapi.115.com
HEADERS:
        Accept-Encoding: gzip, deflate
        Authorization:
        Content-Type: application/x-www-form-urlencoded
        Cookie: acw_tc=
        User-Agent: go-resty/3.0.0-beta.1 (https://resty.dev)
BODY   :
file_name=904+-+HanuMankind+-+Go+To+Sleep%28Explicit%29.flac&file_size=
------------------------------------------------------------------------------
~~~ RESPONSE ~~~
STATUS       : 405 Not Allowed
PROTO        : HTTP/1.1
RECEIVED AT  : 2026-02-04T21:39:34.947164549+08:00
DURATION     : 41.998743ms
HEADERS      :
        Cache-Control: no-cache, no-store
        Connection: keep-alive
        Content-Length: 2657
        Content-Type: text/html; charset=utf-8
        Date: Wed, 04 Feb 2026 13:39:33 GMT
        Pragma: no-cache
        Server: Tengine

### 配置文件内容(必填)

<img width="1528" height="792" alt="Image" src="https://github.com/user-attachments/assets/02acc887-c496-44b7-bacf-8ece1847a6be" />

<img width="1546" height="750" alt="Image" src="https://github.com/user-attachments/assets/c0e1a4d2-1cd1-4f26-8304-ef45856c4ea1" />

### 复现链接(可选)

希望能够针对这种问题进行识别并应对,这种情况任务失败报错的信息啥也没输出让人一头雾水

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure through the /open/upload/init endpoint in the 115开放平台 driver with the two filenames described, then compare the request and response behavior. Done means the affected filename case is handled appropriately or produces a useful error instead of an empty message; no source file or test is named in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.