Skip to content

Update HTTP request pipeline config remarks #36421

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.

Sign up for GitHub

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

Merged
guardrex merged 4 commits into from
Dec 2, 2025
Merged

Update HTTP request pipeline config remarks #36421

Changes from 3 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d1be7d7
Update section on HTTP request pipeline configuration
guardrex Dec 2, 2025
4bd2fbc
Fix capitalization in environment description
guardrex Dec 2, 2025
2c7112a
Update aspnetcore/blazor/tutorials/movie-database-app/part-1.md
guardrex Dec 2, 2025
88d9648
Fix formatting for Development environment mention
guardrex Dec 2, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions aspnetcore/blazor/tutorials/movie-database-app/part-1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -286,9 +286,9 @@ var app = builder.Build();

Next, the HTTP request pipeline is configured.

In the development environment:
When the app isn't running in the Development environment:
Copy link
Contributor

@wadepickett wadepickett Dec 2, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor nit and I could see it either way, but seems like we might use code ticks around "Development" here if it is to be capitalized.

Copy link
Collaborator Author

@guardrex guardrex Dec 2, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've been unable to stick to a convention on this one 😢. I'm going to make a tracking item entry to go through all of the Blazor docs and make it consistent. I'll go code style on the next commit; and with @tdykstra, you can let me know which convention you ultimately settle on. It sounds like for now that we'll code style the environment names.

Copy link
Contributor

@tdykstra tdykstra Dec 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My vote goes for code style.

Copy link
Collaborator Author

@guardrex guardrex Dec 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very well ..... I've been about 50-50 on it one way or the other I'm sorry to say on this one 🙈😆.

Because this is a low priority item to address, I've made a tracking entry on it. I'll circle around later, open an issue, and knock it out.


* Exception Handler Middleware (<xref:Microsoft.AspNetCore.Builder.ExceptionHandlerExtensions.UseExceptionHandler%2A>) processes errors and displays a developer exception page during development app runs.
* Exception Handler Middleware (<xref:Microsoft.AspNetCore.Builder.ExceptionHandlerExtensions.UseExceptionHandler%2A>) processes errors and displays a custom error page.
* [HTTP Strict Transport Security Protocol (HSTS) Middleware](xref:security/enforcing-ssl#http-strict-transport-security-protocol-hsts) (<xref:Microsoft.AspNetCore.Builder.HstsBuilderExtensions.UseHsts%2A>) processes [HSTS](https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Strict_Transport_Security_Cheat_Sheet.html).

```csharp
Expand Down