From eba5133fedde1f9db666f7dbce64ffd994188a00 Mon Sep 17 00:00:00 2001 From: XuqmGroup Date: Mon, 18 May 2026 13:31:11 +0800 Subject: [PATCH] fix: file upload 403 no longer clears token or triggers logout 403 from the file service (e.g. permissions/CORS error) was incorrectly treated as an auth failure, removing the token and redirecting to login. 403 should only show an error message; only 401 indicates an auth failure. Co-Authored-By: Claude Sonnet 4.6 --- tenant-platform/src/api/file.ts | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/tenant-platform/src/api/file.ts b/tenant-platform/src/api/file.ts index 252226e..af4279c 100644 --- a/tenant-platform/src/api/file.ts +++ b/tenant-platform/src/api/file.ts @@ -55,11 +55,7 @@ fileClient.interceptors.response.use( return Promise.reject(error) } if (status === 403) { - localStorage.removeItem('token') - if (router.currentRoute.value.path !== '/login') { - router.push('/login?reason=' + encodeURIComponent('登录已失效，请重新登录')) - } - ElMessage.error(error.response?.data?.message ?? '登录已失效，请重新登录') + ElMessage.error(error.response?.data?.message ?? '无权限执行此操作') return Promise.reject(error) } const msg = error.response?.data?.message ?? '文件请求失败'