AlistGo / AlistGo/alist

挂载115的Alist,复制报错:status":403,"message":"invalid signature"

Open
#7,281 3 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Go
Stars
50.2k
Forks
7.9k
Avg merge
8d 11h
Merged PRs (30d)
7

Description

### Please make sure of the following things

- [X] I'm sure there are no duplicate issues or discussions.
我确定没有重复的issue或讨论。

- [X] I have read the [documentation](https://alist.nn.ci).
我已经阅读了[文档](https://alist.nn.ci)。
- [X] I'm sure it's due to `AList` and not something else(such as [Network](https://alist.nn.ci/faq/howto.html#tls-handshake-timeout-read-connection-reset-by-peer-dns-lookup-failed-connect-connection-refused-client-timeout-exceeded-while-awaiting-headers-no-such-host) ,`Dependencies` or `Operational`).
我确定是`AList`的问题,而不是其他原因(例如[网络](https://alist.nn.ci/zh/faq/howto.html#tls-handshake-timeout-read-connection-reset-by-peer-dns-lookup-failed-connect-connection-refused-client-timeout-exceeded-while-awaiting-headers-no-such-host),`依赖`或`操作`)。

- [X] I'm sure this issue is not fixed in the latest version.
我确定这个问题在最新版本中没有被修复。

### AList Version / AList 版本

v 3.37.4

### Driver used / 使用的存储驱动

115

### Describe the bug / 问题描述

Alist A, 挂载115A,挂载成功。
Alist B,挂载115B,挂载成功。
将AlistA 挂载到AlistB中,并在AlistB中,下载AlistA中的115的文件,成功,可正常下载,或调用Aria2下载。

但在AlistB使用“复制”动作,即去复制挂载的AlistA中的115的文件,将会报错。
错误提示:http request failure, err:http request [https://cdnfhnfdfs.115.com/group821/M00/03/CE/CnUAzFSvZpgAAAAAD9OD0x9hGVk4095447/CpzVol_01.zip?XXXXXX] failure,status: 403 response:{"status":403,"message":"invalid signature","request_id":"66FA5E55EB228436369DE83D"}
而直接无此报错

多次测试可复现,alistA alistB均是最新版

同时也测试复制功能在其他挂载的非115的,则是正常生效,无bug。
也就是说此现象只在115上出现

### Reproduction / 复现链接

### Config / 配置

### Logs / 日志

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the copy action between two AList instances using the 115 driver, comparing it with the working download and non-115 copy paths. Trace the 115 copy request and its generated signed URL; done means copying the mounted 115 file succeeds without the 403 invalid-signature response.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.