Output Cache doesn't work when user has Cookie Authentication cookies

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

After a user logs in to my website using Google/Facebook the output cache doesn’t work anymore due to .AspNetCore.Cookies.

Please change the default policy so only for action/controller that has Authorize on it the output cache will be ignored instead when the user is logged in.

The current behavior is not correct because logged in user views static content that should come from output cache.

Describe the solution you’d like

Change the behavior of the default policy to ignore output only when action/controller has Authorize attribute.

Additional context

No response

[adityamandaleeka]

@offirpeer As @sebastienros mentioned above, the caching policy can be overridden to modify the behavior (including allowing you to enable caching on authenticated requests).

As a platform we try to choose safe defaults where possible to minimize the chance of accidental misuse, so it’s unlikely that we will change the default behavior here.

[sebastienros]

By design and documented, when a user is authenticated output caching is disabled for the request.

Custom routes or actions can use a custom policy that will enable caching even for authenticated requests. Documentation is here: https://learn.microsoft.com/en-us/aspnet/core/performance/caching/output?view=aspnetcore-7.0