mental gorge
I would like to move my Astro server actions to its Astro page. So instead of calling the action from src/action.ts, I want to call it from the server section of the Astro page
`---
`
I need to do this because Astro isn't letting me access "context.cookies.get("data")?.value" successfully....due to cookie path issue. It keeps return undefined in the Astro action. So instead of
How do I simply move the action to the page itself and easily access the cookies value?
@sinful shell
sinful shellBOT
Hi @mental gorge. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
You can move your action logic directly into the server frontmatter (---) of your Astro page and access cookies via Astro.cookies. This is a common pattern for reusing action logic on the server side.
Instead of calling the action from src/actions/index.ts, use Astro.callAction() in your page's frontmatter, or simply inline the logic directly and read cookies with Astro.cookies.get().
---
export const prerender = false; // Required unless you're in 'server' mode
// Access cookies directly in the page frontmatter
const cookieValue = Astro.cookies.get("data")?.value;
// Use the cookie value however you need
console.log(cookieValue);
---
<html>
<body>
<p>Cookie value: {cookieValue}</p>
</body>
</html>
Astro.cookies.get() is available on any on-demand rendered page. [cookies reference]
Astro.callAction()If you still want to keep the action defined in src/actions/index.ts but call it from the page server side, you can use Astro.callAction():
---
import { actions } from 'astro:actions';
const { data, error } = await Astro.callAction(actions.myAction, { /* input */ });
---
This lets you reuse the action logic while having full access to Astro.cookies in the page itself before or after the call. [call actions from components]
Make sure the page has on-demand rendering enabled, otherwise Astro.cookies won't work as expected:
---
export const prerender = false; // Not needed if output is set to 'server'
---
[enabling on-demand rendering]
mental gorge
I'm having serious issue with the cookie path.
Here's my current situation.
I logged in via this path:
`
/appengine/user/[params]/login
// I set the cookie like this in within my action in src/actions.ts
const sessionData = JSON.stringify({ user_id: 1, username: doe, plan: pro });
context.cookies.set('userData', sessionData, {
// path: '/appengine/user' ... I have tried several different paths
httpOnly: true,
secure: true,
maxAge: 60 * 60 * 168 // 1 week
});
return { success: true };
// Now I'm trying to perform an operation here but requires the cookieData
/appengine/user/[same-params]/create-app
const getUserSession = context.cookies.get("user data")?.value;
// getUserSession returns undefined in the action but very available in the "/appengine/user/[same-params]/create-app" page
`
What am I doing wrong?
@sinful shell
sinful shellBOT
Let me check the knowledge base for you again. One moment! :books:
Looking at your code, I can spot the issue immediately — you have a typo in your cookie name.
When setting the cookie, you used:
context.cookies.set('userData', sessionData, { ... });
But when getting the cookie, you used:
context.cookies.get("user data")?.value; // ← note the space!
"userData" ≠ "user data" — the space in the getter means it's looking for a completely different cookie, which doesn't exist, hence undefined.
Fix it to use the same name consistently:
// Setting
context.cookies.set('userData', sessionData, {
httpOnly: true,
secure: true,
maxAge: 60 * 60 * 168
});
// Getting
const getUserSession = context.cookies.get("userData")?.value;
path optionIf after fixing the typo you still have issues, note that when no path is specified, most clients default to the current domain root (/), which means the cookie should be accessible across all paths. [cookie set options]
path like /appengine/user, the cookie will only be sent by the browser for requests under that path. Since your action is likely called via a POST to /_actions/..., a restrictive path could prevent the cookie from being included in that request. Leaving path unset (or setting it to '/') is the safest approach for cross-path access.