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 <noreply@anthropic.com>
This commit is contained in:
@@ -98,9 +98,9 @@ import axios from "axios";
|
|||||||
import MobileTopBar from '@shared/components/mobile/MobileTopBar.vue';
|
import MobileTopBar from '@shared/components/mobile/MobileTopBar.vue';
|
||||||
import MobileBottomNav from '@shared/components/mobile/MobileBottomNav.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({
|
const telegramApi = axios.create({
|
||||||
baseURL: '/api/telegram',
|
baseURL: import.meta.env.BASE_URL + 'api/telegram',
|
||||||
headers: { 'Content-Type': 'application/json' }
|
headers: { 'Content-Type': 'application/json' }
|
||||||
});
|
});
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user