From 1e2516e02216687ab61f7ea0352be363af71a992 Mon Sep 17 00:00:00 2001 From: Claude Agent Date: Tue, 24 Feb 2026 10:02:48 +0000 Subject: [PATCH] fix(telegram): use BASE_URL prefix for IIS sub-app compatibility Replace hardcoded '/api/telegram' with import.meta.env.BASE_URL + 'api/telegram' to match the reports API pattern. In production the base is '/roa2web/' so absolute paths bypassed IIS sub-app routing, causing 404 on generate-code endpoint. Co-Authored-By: Claude Sonnet 4.6 --- src/modules/reports/views/TelegramView.vue | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/modules/reports/views/TelegramView.vue b/src/modules/reports/views/TelegramView.vue index 4853953..d5eab8f 100644 --- a/src/modules/reports/views/TelegramView.vue +++ b/src/modules/reports/views/TelegramView.vue @@ -98,9 +98,9 @@ import axios from "axios"; import MobileTopBar from '@shared/components/mobile/MobileTopBar.vue'; import MobileBottomNav from '@shared/components/mobile/MobileBottomNav.vue'; -// Telegram API uses /api/telegram (separate from reports) +// Telegram API uses BASE_URL prefix for IIS sub-app compatibility (/roa2web/ in prod) const telegramApi = axios.create({ - baseURL: '/api/telegram', + baseURL: import.meta.env.BASE_URL + 'api/telegram', headers: { 'Content-Type': 'application/json' } });