Skip to content

feat(driver): add doubao_new driver#2093

Open
Elegant1E wants to merge 13 commits intoOpenListTeam:mainfrom
Elegant1E:doubao_new
Open

feat(driver): add doubao_new driver#2093
Elegant1E wants to merge 13 commits intoOpenListTeam:mainfrom
Elegant1E:doubao_new

Conversation

@Elegant1E
Copy link

Description / 描述

从上游移植了 doubao_new 驱动

Motivation and Context / 背景

原有的豆包驱动疑似API迁移,无法获得新API后的所有操作更新,也无法进行操作。

这是我提出的issue:Closes #2079

Credits:
Ported from Alist PR: AlistGo/alist#9416
感谢该 PR 作者

How Has This Been Tested? / 测试

通过docker构建移植后的新版本后测试该驱动可以正常使用。

Checklist / 检查清单

  • I have read the CONTRIBUTING document.
    我已阅读 CONTRIBUTING 文档。
  • I have formatted my code with go fmt or prettier.
    我已使用 go fmtprettier 格式化提交的代码。
  • I have added appropriate labels to this PR (or mentioned needed labels in the description if lacking permissions).
    我已为此 PR 添加了适当的标签(如无权限或需要的标签不存在,请在描述中说明,管理员将后续处理)。
  • I have requested review from relevant code authors using the "Request review" feature when applicable.
    我已在适当情况下使用"Request review"功能请求相关代码作者进行审查。
  • I have updated the repository accordingly (If it’s needed).
    我已相应更新了相关仓库(若适用)。

Copy link
Member

@xrgzs xrgzs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

建议直接在原来的豆包上面改,然后给老豆包作废

@Elegant1E
Copy link
Author

建议直接在原来的豆包上面改,然后给老豆包作废

感谢建议,是这样的,我看上游的说法是”不是所有的账户都被迁移到新API,新API正在灰度测试“,所以考虑了一下我没有移除原来的豆包驱动,保持两个驱动同时都在可以保证用户一定可以挂载到openlist。此外新的驱动需要填写的配置需求变更,如果直接覆盖原来的豆包驱动,所有正在使用旧版驱动的用户升级后,现有的存储挂载会立即报错,还是得重新填写驱动配置。综上所述,我不建议直接替换原有豆包驱动。

xrgzs and others added 12 commits February 7, 2026 23:04
Signed-off-by: MadDogOwner <xiaoran@xrgzs.top>
Signed-off-by: MadDogOwner <xiaoran@xrgzs.top>
Signed-off-by: MadDogOwner <xiaoran@xrgzs.top>
Signed-off-by: MadDogOwner <xiaoran@xrgzs.top>
Signed-off-by: MadDogOwner <xiaoran@xrgzs.top>
Signed-off-by: MadDogOwner <xiaoran@xrgzs.top>
Signed-off-by: MadDogOwner <xiaoran@xrgzs.top>
Signed-off-by: MadDogOwner <xiaoran@xrgzs.top>
Signed-off-by: MadDogOwner <xiaoran@xrgzs.top>
@Elegant1E Elegant1E requested a review from xrgzs February 8, 2026 15:29
Copy link
Member

@xrgzs xrgzs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

目前这个驱动的DPoP实现有点问题,这一块需要处理:

  • 不支持自动获取、刷新 Token
  • DPoP Token 签名不规范(网页版也是)
  • 302 会泄露 Token,能够通过泄露的 Token 访问所有文件,存在严重安全问题

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] 豆包无法获得新的内容和路径等更新

2 participants