Why SSR should be turned off?

[pearl trail]

Hi, according to the docs here https://appwrite.io/docs/tutorials/sveltekit-auth/step-4 I should turn off the SSR in my SvelteKit project why is that so? Is it mandatory? What will happen if I turn that on?

[smoky lily]

Because that way you will not face issues with logins and authentication. If you use SSR, for now, you need to get the cookie and handle it manually. That will be improved in next version

[pearl trail]

Awesome, thanks for enlighten me

[trim field]

@pearl trail I faced this issue with Nuxt SSR. https://discord.com/channels/564160730845151244/1203427828066951168

[wooden swift]

Appwrite Auth uses secure HTTP cookies to authorize. That means either browser or SSR server will have the cookie. If you had both enabled, and you had some guard logic (like redirect if not logged in), it could cause unexpected behaviour during SSR. Also, from personal experience, there can occur edgecases that then you need to prevent in code (with code like {#if data.user}).

In general I would personally recommend doing either ssr = false or csr = false in Svelte files +page.js and +layout.js, unless you have very specific use-case when you need both.
EDIT: You can mark your whole app SSR or CSR by doing this just once in your main layout.js, as that the applies to everything below it.

Regarding SSR in general, we will be adding support in next release. While it's supported already, you need a lot of appwrite-specific knowledge to achieve it which is not the experiece we aim for. In next release it will be simple, well documented and with many example demo apps.

[pearl trail]

Thanks, I'll check it out

[pearl trail]

I see, that's why earlier before even if I turned off the SSR but define the logic inside a .server.ts I always get redirected to login page.

Can't wait and try the next release.