Aias00 opened a new issue, #811:
URL: https://github.com/apache/rocketmq-dashboard/issues/811

   ## Problem
   
   The AI chat SSE client calls a hard-coded endpoint:
   
   ```ts
   fetch('/api/ai/chat', ...)
   ```
   
   Other frontend API modules use the shared axios client with `API_BASE_URL`, 
which can be configured by `VITE_API_BASE_URL`. When the Studio frontend is 
deployed with a custom API prefix or non-default reverse proxy path, regular 
API calls use the configured base URL but AI chat streaming still posts to 
`/api/ai/chat`.
   
   ## Expected behavior
   
   `chatStream` should build its SSE URL from the same `API_BASE_URL` config 
used by the rest of the frontend API layer.
   
   ## Scope
   
   Track 3 / AI Native. This only aligns the AI chat streaming endpoint with 
the existing frontend API configuration and should not change SSE parsing 
behavior.
   
   ## Evidence
   
   - `web/src/config.ts` defines `API_BASE_URL`.
   - `web/src/api/client.ts` uses `API_BASE_URL` for axios requests.
   - `web/src/api/ai.ts` hard-codes `fetch('/api/ai/chat', ...)` for streaming 
chat.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to