feat: 前端组件准备
This commit is contained in:
Vendored
+43
@@ -0,0 +1,43 @@
|
||||
// server/api/cache/clear.post.ts - 清空答题缓存接口
|
||||
import { setResponseStatus } from "h3";
|
||||
import { invalidAccessTokenResponse, verifyAccessToken } from "~~/server/utils/auth";
|
||||
import { answerCache } from "~~/server/utils/cache";
|
||||
import { serverEnv } from "~~/server/utils/env";
|
||||
import { createApiLogger } from "~~/server/utils/logging";
|
||||
|
||||
/**
|
||||
* 清空内存缓存
|
||||
*
|
||||
* 这是一个管理类接口,配置 ACCESS_TOKEN 时必须携带正确 token
|
||||
* 清理的是当前 Nuxt 进程内缓存;多实例部署时,每个实例都有自己的内存缓存
|
||||
*/
|
||||
export default defineEventHandler((event) => {
|
||||
const logger = createApiLogger(event, "api.cache.clear");
|
||||
|
||||
// 没配置 token 时保持旧服务的开放行为;配置后用于简单保护管理接口
|
||||
if (!verifyAccessToken(event)) {
|
||||
setResponseStatus(event, 403);
|
||||
logger.warn("invalid_access_token");
|
||||
return {
|
||||
success: false,
|
||||
message: invalidAccessTokenResponse().msg
|
||||
};
|
||||
}
|
||||
|
||||
// 缓存被关闭时不报错,只明确告诉调用方当前没有缓存可清
|
||||
if (!serverEnv.enableCache || !answerCache) {
|
||||
return {
|
||||
success: false,
|
||||
message: "缓存未启用"
|
||||
};
|
||||
}
|
||||
|
||||
// 清空当前进程内缓存,不影响问答记录和运行统计中的 uptime
|
||||
answerCache.clear();
|
||||
logger.info("finish_success");
|
||||
|
||||
return {
|
||||
success: true,
|
||||
message: "缓存已清除"
|
||||
};
|
||||
});
|
||||
Reference in New Issue
Block a user