Skip to content

fix:修复从 cherry-studio 导入备份数据时,请求自定义模型报错#351

Open
Little-LittleProgrammer wants to merge 1 commit intoCherryHQ:mainfrom
Little-LittleProgrammer:fix/model-request-404
Open

fix:修复从 cherry-studio 导入备份数据时,请求自定义模型报错#351
Little-LittleProgrammer wants to merge 1 commit intoCherryHQ:mainfrom
Little-LittleProgrammer:fix/model-request-404

Conversation

@Little-LittleProgrammer

历史逻辑

  1. cherry-studio pc应用里,会经过 formatApiHost 将所有的 apiHost格式化,去掉了末尾的 /
    a. 例如:百炼平台: https://dashscope.aliyuncs.com/compatible-mode/v1
  2. 但是 cherry-studio app 应用里 formatApiHost 会根据 apiHost 是否以 / 结尾判断是否加 /v1/,
  3. 因此,遇到上述情况, cherry-studio-app, 发起请求的最终 url 会处理成 https://dashscope.aliyuncs.com/compatible-mode/v1/v1/chat/completions, 最终导致请求 404

现在逻辑

  1. cherry-studio formatApiHost 的方法迁移过来,增加了多种 api 格式化的分支,具体可参考测试用例

- Add hasAPIVersion function to detect if host already contains API version
- Add withoutTrailingSlash and withoutTrailingSharp helper functions
- Improve formatApiHost to handle edge cases like trailing #, whitespace, etc.
- Update providerConfig to pass supportApiVersion parameter for Gemini
- Add comprehensive unit tests for API formatting utilities

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@Little-LittleProgrammer Little-LittleProgrammer changed the title 修复从 cherry-studio 导入备份数据时,请求自定义模型报错 fix:修复从 cherry-studio 导入备份数据时,请求自定义模型报错 Mar 10, 2026
@eeee0717
Copy link
Collaborator

那直接修改app的formatApiHost逻辑匹配pc端是否可以解决?

@Little-LittleProgrammer
Copy link
Author

Little-LittleProgrammer commented Mar 16, 2026

那直接修改app的formatApiHost逻辑匹配pc端是否可以解决?

现在就是将 pc 端的 formatApiHost 的方法迁移过来,毕竟 pc 端经历了长期的线上验证,已经很稳定了,而且有多种特殊情况的处理机制,如果直接增加匹配 pc逻辑后续可能还要更改

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.

2 participants