Skip to content

[Blazor] Add caching attributes when prerendering interactive components #11445

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
javiercn opened this issue Jun 21, 2019 · 3 comments
Closed
Labels
area-blazor Includes: Blazor, Razor Components bug This issue describes a behavior which is not expected - a bug.

Comments

@javiercn
Copy link
Member

When prerendering blazor server-side applications, we should add no-cache no-store must-revalidate and pragma no-cache to avoid the response being cached an the wrong circuit id being sent on the second response.

I didn't actually ran into this (I thought I did) but this is a good idea to do.

@Eilon Eilon added the area-blazor Includes: Blazor, Razor Components label Jun 21, 2019
@mkArtakMSFT mkArtakMSFT added this to the 3.0.0-preview9 milestone Jun 21, 2019
@mkArtakMSFT mkArtakMSFT added PRI: 1 - Required bug This issue describes a behavior which is not expected - a bug. labels Jun 21, 2019
@SteveSandersonMS
Copy link
Member

I think this can just be closed due to removing stateful prerendering (#12245).

@javiercn
Copy link
Member Author

Should we do this based on the current user identity even if we don't do interactive? (At least for authenticated users)

@mkArtakMSFT
Copy link
Member

Closing this as as this is for interactive prerendering, which we're removing.

@ghost ghost locked as resolved and limited conversation to collaborators Dec 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components bug This issue describes a behavior which is not expected - a bug.
Projects
None yet
Development

No branches or pull requests

4 participants