getServerSession killing nextjs cache?

nextauthjs / next-auth

Authentication for the Web.

ISC License

24.78k stars 3.49k forks source link

Environment

System: OS: Windows 10 10.0.19045 CPU: (6) x64 Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz Memory: 7.97 GB / 15.94 GB Binaries: Node: 18.17.0 - C:\Program Files\nodejs\node.EXE Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD npm: 9.6.7 - C:\Program Files\nodejs\npm.CMD Browsers: Edge: Spartan (44.19041.3636.0), Chromium (120.0.2210.61) Internet Explorer: 11.0.19041.3636 npmPackages: @auth/core: ^0.18.4 => 0.18.4 @auth/prisma-adapter: ^1.0.9 => 1.0.9 next: ^14.0.4 => 14.0.4 next-auth: ^5.0.0-beta.4 => 5.0.0-beta.4 react: ^18.2.0 => 18.2.0

Reproduction URL

Describe the issue

i using getServerSession/auth to get user informations and then kill completly nextjs13/14 fetch() cache

How to reproduce

here is complete scenario:

i using getServerSession in layout.tsx(server component), to fullfill my navbar(client component) with user informations. Then in the page.tsx i make 2 calls(1 for article and another for comments).

await fetch(http:localhost:3000/api/posts/${username}/${slug})

and comments.tsx (server component) are inside a a

await fetch(http:localhost:3000/api/comments?postId=${postId}&page=${page}, { next: { tags: ['comments'] } })

when i invoke getServerSession in layout every refresh on page calls my apis again (i put a log there). But if i remove getServerSession from layout and use useSession() directly in navbar.tsx(client component) the fetch uses cache and not call my api again, just after a revalidate.

here are the header list logged in my api

HeadersList {
  cookies: null,
  [Symbol(headers map)]: Map(11) {
    'accept' => { name: 'accept', value: '*/*' },
    'accept-encoding' => { name: 'accept-encoding', value: 'gzip, deflate' },
    'accept-language' => { name: 'accept-language', value: '*' },
    'connection' => { name: 'connection', value: 'keep-alive' },
    'host' => { name: 'host', value: 'localhost:3000' },
    'sec-fetch-mode' => { name: 'sec-fetch-mode', value: 'cors' },
    'user-agent' => { name: 'user-agent', value: 'undici' },
    'x-forwarded-for' => { name: 'x-forwarded-for', value: '::1' },
    'x-forwarded-host' => { name: 'x-forwarded-host', value: 'localhost:3000' },
    'x-forwarded-port' => { name: 'x-forwarded-port', value: '3000' },
    'x-forwarded-proto' => { name: 'x-forwarded-proto', value: 'http' }
  },
  [Symbol(headers map sorted)]: [
    [ 'accept', '*/*' ],
    [ 'accept-encoding', 'gzip, deflate' ],
    [ 'accept-language', '*' ],
    [ 'connection', 'keep-alive' ],
    [ 'host', 'localhost:3000' ],
    [ 'sec-fetch-mode', 'cors' ],
    [ 'user-agent', 'undici' ],
    [ 'x-forwarded-for', '::1' ],
    [ 'x-forwarded-host', 'localhost:3000' ],
    [ 'x-forwarded-port', '3000' ],
    [ 'x-forwarded-proto', 'http' ]
  ]
}

Expected behavior

not interfere on nextjs13/14 fetch cache configurations

We could not detect a valid reproduction link. Make sure to follow the bug report template carefully.

Why was this issue closed?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We need a link to a public GitHub repository. Example: (NextAuth.js example repository).

The bug template that you filled out has a section called "Reproduction URL", which is where you should provide the link to the reproduction.

If you did not provide a link or the link you provided is not valid, we will close the issue.
If you provide a link to a private repository, we will close the issue.
If you provide a link to a repository but not in the correct section, we will close the issue.

What should I do?

Depending on the reason the issue was closed, you can do the following:

If you did not provide a link, please open a new issue with a link to a reproduction.
If you provided a link to a private repository, please open a new issue with a link to a public repository.
If you provided a link to a repository but not in the correct section, please open a new issue with a link to a reproduction in the correct section.

In general, assume that we should not go through a lengthy onboarding process at your company code only to be able to verify an issue.

My repository is private and cannot make it public

In most cases, a private repo will not be a sufficient minimal reproduction, as this codebase might contain a lot of unrelated parts that would make our investigation take longer. Please do not make it public. Instead, create a new repository using the templates above, adding the relevant code to reproduce the issue. Common things to look out for:

Remove any code that is not related to the issue. (pages, API Routes, components, etc.)
Remove any dependencies that are not related to the issue.
Remove any third-party service that would require us to sign up for an account to reproduce the issue.
Remove any environment variables that are not related to the issue.
Remove private packages that we do not have access to.
If the issue is not related to a monorepo specifically, try to reproduce the issue without a complex monorepo setup

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps by opening a new issue.

I think my reproduction is good enough, why aren't you looking into it quickly?

We look into every issue and monitor open issues for new comments.

However, sometimes we might miss a few due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

nextauthjs / next-auth