Skip to content
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

Remark on CRIME/BREACH in route param and query string guidance #31916

Closed
guardrex opened this issue Feb 27, 2024 · 0 comments · Fixed by #32096
Closed

Remark on CRIME/BREACH in route param and query string guidance #31916

guardrex opened this issue Feb 27, 2024 · 0 comments · Fixed by #32096

Comments

@guardrex
Copy link
Collaborator

guardrex commented Feb 27, 2024

Description

Here and in the Components overview, let's warn off of reproducing route param values and query string values in responses. Generally recommend that devs should avoid rendering components that contain sensitive information alongside components that can render data from untrusted sources (JS interop, database data provided by a user, route param, QS, etc.).

Page URL

https://learn.microsoft.com/en-us/aspnet/core/blazor/fundamentals/routing?view=aspnetcore-8.0

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/fundamentals/routing.md

Document ID

b6cb2574-6326-a40d-0b6c-d1661328e828

Article author

@guardrex

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants