F
PFF
KK
BYou cannot set Cache-Control headers in next.config.js for pages or assets, as these headers will be overwritten in production to ensure that responses and static assets are cached effectively.
B
KKFF
AAKKKKKKKA
ZZZ
responseMeta()export hander() {
...
const jobApplicationSenderEmails =
await getJobApplicationSenderEmailsContextCached();
const jobRoles = await getJobRolesContextCached();
const jobApplicationKeywordIdentifiers =
await getJobApplicationKeywordIdentifiersContextCached();
...
}
// Cached queries
export const getJobApplicationSenderEmailsContextCached = unstable_cache(
async () => {
return await api.jobApplication.getAllSenderEmails();
},
["job-application-sender-emails-context"],
{ revalidate: 60 * 60 },
);
export const getJobRolesContextCached = unstable_cache(
async () => {
return await api.jobApplication.getAllJobRoles();
},
["job-application-roles-context"],
{
revalidate: 60 * 60,
},
);
export const getJobApplicationKeywordIdentifiersContextCached = unstable_cache(
async () => {
return await api.jobApplication.getAllKeywordIdentifiers();
},
["job-application-keyword-identifiers-context"],
{
revalidate: 60 * 60,
},
);// next.config.js
headers: async () => {
return [
{
source: "/api/trpc/yourRouteName",
headers: [
{
key: "Cache-Control",
value: "public, s-maxage=90, max-age=90",
},
],
},
];
},