关键修复:移除root.tsx中Dify环境变量注入
问题:root.tsx 将 NEXT_PUBLIC_API_URL, NEXT_PUBLIC_APP_ID, NEXT_PUBLIC_APP_KEY 注入到客户端 window.__ENV,导致客户端 仍然使用环境变量中的 Dify 直连地址 修改: - 移除 ENV 对象中的所有 Dify 相关环境变量 - 客户端不再从 window.__ENV 读取 Dify 配置 - 确保客户端只使用 /api 路由 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
+4
-4
@@ -140,16 +140,16 @@ export async function loader({ request }: LoaderFunctionArgs) {
|
||||
responseHeaders["Set-Cookie"] = await sessionStorage.commitSession(refreshedSession);
|
||||
}
|
||||
|
||||
// 向组件传递认证状态、当前路径和环境变量
|
||||
// 向组件传递认证状态、当前路径
|
||||
// 注意:不再传递 Dify 相关环境变量,客户端改为调用 Remix API routes
|
||||
return Response.json({
|
||||
isAuthenticated,
|
||||
userRole,
|
||||
pathname,
|
||||
frontendJWT,
|
||||
ENV: {
|
||||
NEXT_PUBLIC_API_URL: process.env.NEXT_PUBLIC_API_URL,
|
||||
NEXT_PUBLIC_APP_ID: process.env.NEXT_PUBLIC_APP_ID,
|
||||
NEXT_PUBLIC_APP_KEY: process.env.NEXT_PUBLIC_APP_KEY,
|
||||
// 移除 NEXT_PUBLIC_API_URL, NEXT_PUBLIC_APP_ID, NEXT_PUBLIC_APP_KEY
|
||||
// 客户端不再需要直接调用 Dify API
|
||||
},
|
||||
}, {
|
||||
headers: responseHeaders
|
||||
|
||||
Reference in New Issue
Block a user