fix(initialization): surface upstream and SSRF errors verbatim in test-connection responses

Test-connection's "连接失败" was nearly useless for debugging because
two layers conspired to swallow the actual upstream error:

Backend swallow
---------------
checkChatModelConnection and CheckASRModel pattern-matched on the
upstream error string (401 / 404 / timeout / ...) and replaced it with
a fixed Chinese hint. The original SDK message (request URL, response
body, provider's error code description) was discarded.

Refactor: extract classifyConnectionError(errMsg) — returns just the
short Chinese hint. Callers combine "<hint>:<raw err>" so the hint
indicates "where to start looking" and the raw error shows "what
actually happened". The status-400 special-case (endpoint reachable,
parameter mismatch only) still returns success.

Frontend swallow
----------------
ModelEditorDialog.testConnection ignored result.message on success
paths (fine), but also overwrote it with a generic i18n string on
failure paths and 4xx rejections — even though axios's interceptor
already lifts the backend's error.message to error.message. Failure
branch now uses error?.message || result.message as the toast content;
i18n fallback only when neither is present.

SSRF allowlist hint
-------------------
SSRF validation failures previously returned
"Base URL 未通过安全校验: <reason>" with no mention of how to recover
(the allowlist is server-side, not configurable in the UI). Operators
hit it and were stuck.

New utils.FormatSSRFError(label, rawURL, err) wraps the error with
guidance to add the host to SSRF_WHITELIST_EXTRA (the operator-facing
append-only escape hatch — SSRF_WHITELIST itself is the project's
baseline). The hint echoes the failed host so it can be copy-pasted
straight into the env var:

  Base URL 未通过安全校验:DNS resolution failed for hostname
  test.local.com ... 如该地址确实可信,请联系运维在服务端环境变量
  SSRF_WHITELIST_EXTRA 中加入该主机(支持精确域名 / *.example.com
  通配 / IP / CIDR),示例:SSRF_WHITELIST_EXTRA=test.local.com,
  *.example.com,10.0.0.0/8

All SSRF call sites switch to the helper:
  initialization (CheckRemoteModel / TestEmbedding / CheckRerank /
  CheckASR / TestMultimodal / batch validation), model CRUD,
  mcp_service CRUD, knowledge URL ingest, system ReconnectDocReader.
This commit is contained in:
wizardchen
2026-05-17 15:10:42 +08:00
committed by lyingbug
parent 31d5566a50
commit ce8969ab14
7 changed files with 107 additions and 41 deletions
+12 -9
View File
@@ -1034,24 +1034,27 @@ const checkRemoteAPI = async () => {
remoteChecked.value = true
remoteAvailable.value = result.available || false
// Always use i18n for display; backend message is for debugging only
if (result.message) {
console.debug('Backend message:', result.message)
}
remoteMessage.value = result.available
? t('model.editor.connectionSuccess')
: t('model.editor.connectionFailed')
// 之前这里把 backend 的错误 message 只丢到 console.debug,用户只能
// 看到通用的 "连接失败" toast,根本看不出是 401 / 404 / 模型不存在
// 还是别的什么。改成:成功时用 i18n 通用提示;失败时直接展示后端
// 给到的具体原因(已经在后端 classifyConnectionError 中包了一层
// 易读的中文 hint + 原始 SDK 报错),方便排查。
if (result.available) {
remoteMessage.value = t('model.editor.connectionSuccess')
MessagePlugin.success(remoteMessage.value)
} else {
remoteMessage.value = result.message || t('model.editor.connectionFailed')
console.debug('Backend message:', result.message)
MessagePlugin.error(remoteMessage.value)
}
} catch (error: any) {
console.error('Remote API check failed:', error)
remoteChecked.value = true
remoteAvailable.value = false
remoteMessage.value = t('model.editor.connectionConfigError')
// 后端 4xx/5xx(如 SSRF 校验失败)会走到这里。axios 拦截器把后端
// { error: { message: "..." } } 提到了 error.message,里面已经包含
// 易读 hint + 原因,直接展示出来,比通用 "请检查配置" 有用得多。
remoteMessage.value = error?.message || t('model.editor.connectionConfigError')
MessagePlugin.error(remoteMessage.value)
} finally {
checking.value = false