takes precedence for browser-based address routing problems, such as an incorrect URL typed into the browser's address bar or selecting a link that has no endpoint in the app.
@@ -344,7 +344,7 @@ To provide Not Found content for global interactive rendering, use a Not Found p
Sorry, the content you are looking for does not exist.
```
-The `NotFound` component is assigned to , which supports routing that can be used across Status Code Pages Re-execution Middleware, including non-Blazor middleware.
+The `NotFound` component is assigned to , which supports routing that can be used across status code pages re-execution middleware, including non-Blazor middleware.
In the following example, the preceding `NotFound` component is present in the app's `Pages` folder and passed to the parameter:
diff --git a/aspnetcore/blazor/fundamentals/routing.md b/aspnetcore/blazor/fundamentals/routing.md
index f7f0b0bab23c..92c54a978fd0 100644
--- a/aspnetcore/blazor/fundamentals/routing.md
+++ b/aspnetcore/blazor/fundamentals/routing.md
@@ -188,7 +188,7 @@ The Blazor project template includes a `NotFound.razor` page. This page automati
Sorry, the content you are looking for does not exist.
```
-The `NotFound` component is assigned to the router's parameter, which supports routing that can be used across Status Code Pages Re-execution Middleware, including non-Blazor middleware.
+The `NotFound` component is assigned to the router's parameter, which supports routing that can be used across status code pages re-execution middleware, including non-Blazor middleware.
In the following example, the preceding `NotFound` component is present in the app's `Pages` folder and passed to the parameter:
diff --git a/aspnetcore/blazor/fundamentals/signalr.md b/aspnetcore/blazor/fundamentals/signalr.md
index 957de92a4829..745188d3acb2 100644
--- a/aspnetcore/blazor/fundamentals/signalr.md
+++ b/aspnetcore/blazor/fundamentals/signalr.md
@@ -109,7 +109,7 @@ This provides a clean, type-safe API for configuring SignalR connection settings
## Disable response compression for Hot Reload
-When using [Hot Reload](xref:test/hot-reload), disable Response Compression Middleware in the `Development` environment. Whether or not the default code from a project template is used, always call first in the request processing pipeline.
+When using [Hot Reload](xref:test/hot-reload), disable response compression middleware in the `Development` environment. Whether or not the default code from a project template is used, always call first in the request processing pipeline.
In the `Program` file:
diff --git a/aspnetcore/blazor/fundamentals/startup.md b/aspnetcore/blazor/fundamentals/startup.md
index bc768a88d127..a69013dcf2f3 100644
--- a/aspnetcore/blazor/fundamentals/startup.md
+++ b/aspnetcore/blazor/fundamentals/startup.md
@@ -572,7 +572,7 @@ In the following examples, a [Content Security Policy (CSP)](https://developer.m
### Server-side and prerendered client-side scenarios
-Use [ASP.NET Core Middleware](xref:fundamentals/middleware/index) to control the headers collection.
+Use [ASP.NET Core middleware](xref:fundamentals/middleware/index) to control the headers collection.
:::moniker range=">= aspnetcore-6.0"
diff --git a/aspnetcore/blazor/fundamentals/static-files.md b/aspnetcore/blazor/fundamentals/static-files.md
index 253f4ed7c783..45712db4237e 100644
--- a/aspnetcore/blazor/fundamentals/static-files.md
+++ b/aspnetcore/blazor/fundamentals/static-files.md
@@ -60,7 +60,7 @@ Serving static assets is managed by either routing endpoint conventions or a mid
Feature | API | .NET Version | Description
--- | --- | :---: | ---
Map Static Assets routing endpoint conventions | | .NET 9 or later | Optimizes the delivery of static assets to clients.
-Static File Middleware | | All .NET versions | Serves static assets to clients without the optimizations of Map Static Assets but useful for some tasks that Map Static Assets isn't capable of managing.
+Static file middleware | | All .NET versions | Serves static assets to clients without the optimizations of Map Static Assets but useful for some tasks that Map Static Assets isn't capable of managing.
Map Static Assets can replace in most situations. However, Map Static Assets is optimized for serving the assets from known locations in the app at build and publish time. If the app serves assets from other locations, such as disk or embedded resources, should be used.
@@ -73,7 +73,7 @@ When [Interactive WebAssembly or Interactive Auto render modes](xref:blazor/fund
* During WebAssembly boot, Blazor retrieves the URL, imports the module, and calls a function to retrieve the asset collection and reconstruct it in memory. The URL is specific to the content and cached forever, so this overhead cost is only paid once per user until the app is updated.
* The resource collection is also exposed at a human-readable URL (`_framework/resource-collection.js`), so JS has access to the resource collection for [enhanced navigation](xref:blazor/fundamentals/navigation#enhanced-navigation-and-form-handling) or to implement features of other frameworks and third-party components.
-Static File Middleware () is useful in the following situations that Map Static Assets () can't handle:
+Static file middleware () is useful in the following situations that Map Static Assets () can't handle:
* Serving files from disk that aren't part of the build or publish process, for example, files added to the application folder during or after deployment.
* Applying a path prefix to Blazor WebAssembly static asset files, which is covered in the [Prefix for Blazor WebAssembly assets](#prefix-for-blazor-webassembly-assets) section.
@@ -229,9 +229,9 @@ For examples of how to address the policy violation with Subresource Integrity (
:::moniker range="< aspnetcore-9.0"
-Configure Static File Middleware to serve static assets to clients by calling in the app's request processing pipeline. For more information, see .
+Configure static file middleware to serve static assets to clients by calling in the app's request processing pipeline. For more information, see .
-In releases prior to .NET 8, Blazor framework static files, such as the Blazor script, are served via Static File Middleware. In .NET 8 or later, Blazor framework static files are mapped using endpoint routing, and Static File Middleware is no longer used.
+In releases prior to .NET 8, Blazor framework static files, such as the Blazor script, are served via static file middleware. In .NET 8 or later, Blazor framework static files are mapped using endpoint routing, and static file middleware is no longer used.
:::moniker-end
@@ -506,7 +506,7 @@ To create additional file mappings with a to execute a custom Static File Middleware:
+* You can avoid interfering with serving `_framework/blazor.server.js` by using to execute a custom static file middleware:
```csharp
app.MapWhen(ctx => !ctx.Request.Path
diff --git a/aspnetcore/blazor/globalization-localization.md b/aspnetcore/blazor/globalization-localization.md
index 23698c73b75e..9475b2b2f83c 100644
--- a/aspnetcore/blazor/globalization-localization.md
+++ b/aspnetcore/blazor/globalization-localization.md
@@ -306,7 +306,7 @@ In ***client-side development***, dynamically setting the culture from the `Acce
> [!NOTE]
> If the app's specification requires limiting the supported cultures to an explicit list, see the [Dynamically set the client-side culture by user preference](#dynamically-set-the-client-side-culture-by-user-preference) section of this article.
-Apps are localized using [Localization Middleware](xref:fundamentals/localization#localization-middleware). Add localization services to the app with .
+Apps are localized using [localization middleware](xref:fundamentals/localization#localization-middleware). Add localization services to the app with .
Add the following line to the `Program` file where services are registered:
@@ -316,13 +316,13 @@ builder.Services.AddLocalization();
:::moniker range=">= aspnetcore-8.0"
-In ***server-side development***, specify the app's supported cultures before any middleware that might check the request culture. Generally, place Request Localization Middleware immediately before calling . The following example configures supported cultures for United States English and Costa Rican Spanish:
+In ***server-side development***, specify the app's supported cultures before any middleware that might check the request culture. Generally, place localization middleware immediately before calling . The following example configures supported cultures for United States English and Costa Rican Spanish:
:::moniker-end
:::moniker range="< aspnetcore-8.0"
-In ***server-side development***, specify the app's supported cultures immediately after Routing Middleware () is added to the processing pipeline. The following example configures supported cultures for United States English and Costa Rican Spanish using the following API:
+In ***server-side development***, specify the app's supported cultures immediately after routing middleware () is added to the processing pipeline. The following example configures supported cultures for United States English and Costa Rican Spanish using the following API:
* adds the set of the supported cultures for *globalization* (date, number, and currency formatting).
* adds the set of the supported UI cultures *for localization* (translated UI strings for rendering content).
@@ -355,7 +355,7 @@ app.UseRequestLocalization(localizationOptions);
In the preceding example, [`CultureTypes.SpecificCultures`](xref:System.Globalization.CultureTypes) returns only cultures that are specific to a country or region—such as `en-US` or `fr-FR`—which come with full, concrete globalization data (for dates, numbers, calendars, and other cultural UI) that .NET can use for accurate formatting and parsing. Neutral cultures, such as `en` or `fr`, may not have complete globalization data, so they aren't included in this list.
-For information on ordering the Localization Middleware in the middleware pipeline of the `Program` file, see .
+For information on ordering the localization middleware in the middleware pipeline of the `Program` file, see .
Use the `CultureExample1` component shown in the [Demonstration component](#demonstration-component) section to study how globalization works. Issue a request with United States English (`en-US`). Switch to Costa Rican Spanish (`es-CR`) in the browser's language settings. Request the webpage again.
@@ -469,7 +469,7 @@ Use the `CultureExample1` component shown in the [Demonstration component](#demo
:::moniker range=">= aspnetcore-6.0"
-Server-side apps are localized using [Localization Middleware](xref:fundamentals/localization#localization-middleware). Add localization services to the app with .
+Server-side apps are localized using [localization middleware](xref:fundamentals/localization#localization-middleware). Add localization services to the app with .
In the `Program` file:
@@ -481,13 +481,13 @@ builder.Services.AddLocalization();
:::moniker range=">= aspnetcore-8.0"
-Specify the static culture in the `Program` file before any middleware that might check the request culture. Generally, place Request Localization Middleware immediately before . The following example configures United States English:
+Specify the static culture in the `Program` file before any middleware that might check the request culture. Generally, place localization middleware immediately before . The following example configures United States English:
:::moniker-end
:::moniker range=">= aspnetcore-6.0 < aspnetcore-8.0"
-Specify the static culture in the `Program` file immediately after Routing Middleware () is added to the processing pipeline. The following example configures United States English:
+Specify the static culture in the `Program` file immediately after routing middleware () is added to the processing pipeline. The following example configures United States English:
:::moniker-end
@@ -499,13 +499,13 @@ app.UseRequestLocalization("en-US");
The culture value for must conform to the [BCP-47 language tag format](https://www.rfc-editor.org/info/bcp47).
-For information on ordering the Localization Middleware in the middleware pipeline of the `Program` file, see .
+For information on ordering the localization middleware in the middleware pipeline of the `Program` file, see .
:::moniker-end
:::moniker range="< aspnetcore-6.0"
-Server-side apps are localized using [Localization Middleware](xref:fundamentals/localization#localization-middleware). Add localization services to the app with .
+Server-side apps are localized using [localization middleware](xref:fundamentals/localization#localization-middleware). Add localization services to the app with .
In `Startup.ConfigureServices` (`Startup.cs`):
@@ -513,7 +513,7 @@ In `Startup.ConfigureServices` (`Startup.cs`):
services.AddLocalization();
```
-Specify the static culture in `Startup.Configure` (`Startup.cs`) immediately after Routing Middleware is added to the processing pipeline. The following example configures United States English:
+Specify the static culture in `Startup.Configure` (`Startup.cs`) immediately after routing middleware is added to the processing pipeline. The following example configures United States English:
```csharp
app.UseRequestLocalization("en-US");
@@ -521,7 +521,7 @@ app.UseRequestLocalization("en-US");
The culture value for must conform to the [BCP-47 language tag format](https://www.rfc-editor.org/info/bcp47).
-For information on ordering the Localization Middleware in the middleware pipeline of `Startup.Configure`, see .
+For information on ordering the localization middleware in the middleware pipeline of `Startup.Configure`, see .
:::moniker-end
@@ -750,7 +750,7 @@ Add the [`Microsoft.Extensions.Localization` package](https://www.nuget.org/pack
[!INCLUDE[](~/includes/package-reference.md)]
-Server-side apps are localized using [Localization Middleware](xref:fundamentals/localization#localization-middleware). Add localization services to the app with .
+Server-side apps are localized using [localization middleware](xref:fundamentals/localization#localization-middleware). Add localization services to the app with .
In the `Program` file:
@@ -768,7 +768,7 @@ Before the call to ) is added to the request processing pipeline, place the following code:
+After routing middleware () is added to the request processing pipeline, place the following code:
:::moniker-end
@@ -782,9 +782,9 @@ var localizationOptions = new RequestLocalizationOptions()
app.UseRequestLocalization(localizationOptions);
```
-For information on ordering the Localization Middleware in the middleware pipeline, see .
+For information on ordering the localization middleware in the middleware pipeline, see .
-The following example shows how to set the current culture in a cookie that can be read by the Localization Middleware.
+The following example shows how to set the current culture in a cookie that can be read by the localization middleware.
:::moniker range=">= aspnetcore-8.0"
@@ -845,7 +845,7 @@ Add the following to the file:
:::moniker-end
-For information on ordering the Localization Middleware in the middleware pipeline, see .
+For information on ordering the localization middleware in the middleware pipeline, see .
If the app isn't configured to process controller actions:
@@ -1338,7 +1338,7 @@ Add the [`Microsoft.Extensions.Localization` package](https://www.nuget.org/pack
[!INCLUDE[](~/includes/package-reference.md)]
-Server-side apps are localized using [Localization Middleware](xref:fundamentals/localization#localization-middleware). Add localization services to the app with .
+Server-side apps are localized using [localization middleware](xref:fundamentals/localization#localization-middleware). Add localization services to the app with .
In the server project's `Program` file where services are registered:
@@ -1360,7 +1360,7 @@ var localizationOptions = new RequestLocalizationOptions()
app.UseRequestLocalization(localizationOptions);
```
-The following example shows how to set the current culture in a cookie that can be read by the Localization Middleware.
+The following example shows how to set the current culture in a cookie that can be read by the localization middleware.
The following namespaces are required for the `App` component:
@@ -1496,7 +1496,7 @@ builder.Services.AddLocalization();
### Server-side localization
-Use [Localization Middleware](xref:fundamentals/localization#localization-middleware) to set the app's culture.
+Use [localization middleware](xref:fundamentals/localization#localization-middleware) to set the app's culture.
If the app doesn't already support dynamic culture selection:
@@ -1513,13 +1513,13 @@ builder.Services.AddLocalization();
:::moniker range=">= aspnetcore-8.0"
-Place Request Localization Middleware before any middleware that might check the request culture. Generally, place the middleware immediately before calling :
+Place localization middleware before any middleware that might check the request culture. Generally, place the middleware immediately before calling :
:::moniker-end
:::moniker range=">= aspnetcore-6.0 < aspnetcore-8.0"
-Immediately after Routing Middleware () is added to the processing pipeline:
+Immediately after routing middleware () is added to the processing pipeline:
:::moniker-end
@@ -1535,7 +1535,7 @@ var localizationOptions = new RequestLocalizationOptions()
app.UseRequestLocalization(localizationOptions);
```
-For information on ordering the Localization Middleware in the middleware pipeline, see .
+For information on ordering the localization middleware in the middleware pipeline, see .
:::moniker-end
@@ -1550,7 +1550,7 @@ In `Startup.ConfigureServices` (`Startup.cs`):
services.AddLocalization();
```
-In `Startup.Configure` immediately after Routing Middleware () is added to the processing pipeline:
+In `Startup.Configure` immediately after routing middleware () is added to the processing pipeline:
```csharp
var supportedCultures = new[] { "en-US", "es-CR" };
@@ -1562,7 +1562,7 @@ var localizationOptions = new RequestLocalizationOptions()
app.UseRequestLocalization(localizationOptions);
```
-For information on ordering the Localization Middleware in the middleware pipeline of `Startup.Configure`, see .
+For information on ordering the localization middleware in the middleware pipeline of `Startup.Configure`, see .
:::moniker-end
diff --git a/aspnetcore/blazor/host-and-deploy/app-base-path.md b/aspnetcore/blazor/host-and-deploy/app-base-path.md
index 6ac3187572b2..14de89e8256c 100644
--- a/aspnetcore/blazor/host-and-deploy/app-base-path.md
+++ b/aspnetcore/blazor/host-and-deploy/app-base-path.md
@@ -246,7 +246,7 @@ In many hosting scenarios, the relative URL path to the app is the root of the a
:::moniker-end
> [!NOTE]
-> When using (see ), [`app.UseRouting`](xref:Microsoft.AspNetCore.Builder.EndpointRoutingApplicationBuilderExtensions.UseRouting%2A) must be called after so that the Routing Middleware can observe the modified path before matching routes. Otherwise, routes are matched before the path is rewritten by as described in the and .
+> When using (see ), [`app.UseRouting`](xref:Microsoft.AspNetCore.Builder.EndpointRoutingApplicationBuilderExtensions.UseRouting%2A) must be called after so that the routing middleware can observe the modified path before matching routes. Otherwise, routes are matched before the path is rewritten by as described in the and .
Don't prefix links throughout the app with a forward slash. Either avoid the use of a path segment separator or use dot-slash (`./`) relative path notation:
@@ -265,7 +265,7 @@ Don't prefix [Navigation Manager](xref:blazor/fundamentals/navigation#uri-and-na
* ✔️ Correct: `Navigation.NavigateTo("other");`
* ✔️ Correct: `Navigation.NavigateTo("./other");`
-In typical configurations for Azure/IIS hosting, additional configuration usually isn't required. In some non-IIS hosting and reverse proxy hosting scenarios, additional Static File Middleware configuration might be required:
+In typical configurations for Azure/IIS hosting, additional configuration usually isn't required. In some non-IIS hosting and reverse proxy hosting scenarios, additional static file middleware configuration might be required:
* To serve static files correctly (for example, `app.UseStaticFiles("/CoolApp");`).
* To serve the Blazor script (`_framework/blazor.*.js`). For more information, see .
diff --git a/aspnetcore/blazor/host-and-deploy/index.md b/aspnetcore/blazor/host-and-deploy/index.md
index 8ccd5f98fc33..140094c852b2 100644
--- a/aspnetcore/blazor/host-and-deploy/index.md
+++ b/aspnetcore/blazor/host-and-deploy/index.md
@@ -161,7 +161,7 @@ In scenarios where an app requires a separate area with custom resources and Raz
* `~/css/site.css`
* `~/BlazorSample.styles.css` (the example app's namespace is `BlazorSample`)
* `~/_framework/blazor.server.js` (Blazor script)
-* If the area should have its own static asset folder, add the folder and specify its location to Static File Middleware in `Program.cs` (for example, `app.UseStaticFiles("/Admin/wwwroot")`).
+* If the area should have its own static asset folder, add the folder and specify its location to static file middleware in `Program.cs` (for example, `app.UseStaticFiles("/Admin/wwwroot")`).
* Razor components are added to the area's folder. At a minimum, add an `Index` component to the area folder with the correct `@page` directive for the area. For example, add a `Pages/Admin/Index.razor` file based on the app's default `Pages/Index.razor` file. Indicate the Admin area as the route template at the top of the file (`@page "/admin"`). Add additional components as needed. For example, `Pages/Admin/Component1.razor` with an `@page` directive and route template of `@page "/admin/component1`.
* In `Program.cs`, call for the area's request path immediately before the fallback root page path to the `_Host` page:
diff --git a/aspnetcore/blazor/host-and-deploy/webassembly/multiple-hosted-webassembly.md b/aspnetcore/blazor/host-and-deploy/webassembly/multiple-hosted-webassembly.md
index 30715c5e9bdb..adc2ffe9cccf 100644
--- a/aspnetcore/blazor/host-and-deploy/webassembly/multiple-hosted-webassembly.md
+++ b/aspnetcore/blazor/host-and-deploy/webassembly/multiple-hosted-webassembly.md
@@ -196,7 +196,7 @@ In the server app's `Program.cs` file, remove the following code, which appears
- app.MapFallbackToFile("index.html");
```
- Leave Static File Middleware in place:
+ Leave static file middleware in place:
```csharp
app.UseStaticFiles();
diff --git a/aspnetcore/blazor/security/additional-scenarios.md b/aspnetcore/blazor/security/additional-scenarios.md
index 582b547ae980..1cebf40c5e52 100644
--- a/aspnetcore/blazor/security/additional-scenarios.md
+++ b/aspnetcore/blazor/security/additional-scenarios.md
@@ -478,13 +478,13 @@ In a component that presents a **Logout** button to authorized users:
:::moniker range=">= aspnetcore-6.0"
-For an app that uses more than one Authentication Middleware and thus has more than one authentication scheme, the scheme that Blazor uses can be explicitly set in the endpoint configuration of the `Program` file. The following example sets the OpenID Connect (OIDC) scheme:
+For an app that uses more than one authentication middleware and thus has more than one authentication scheme, the scheme that Blazor uses can be explicitly set in the endpoint configuration of the `Program` file. The following example sets the OpenID Connect (OIDC) scheme:
:::moniker-end
:::moniker range="< aspnetcore-6.0"
-For an app that uses more than one Authentication Middleware and thus has more than one authentication scheme, the scheme that Blazor uses can be explicitly set in the endpoint configuration of `Startup.cs`. The following example sets the OpenID Connect (OIDC) scheme:
+For an app that uses more than one authentication middleware and thus has more than one authentication scheme, the scheme that Blazor uses can be explicitly set in the endpoint configuration of `Startup.cs`. The following example sets the OpenID Connect (OIDC) scheme:
:::moniker-end
@@ -523,7 +523,7 @@ app.MapBlazorHub().RequireAuthorization(
:::moniker range="< aspnetcore-5.0"
-For an app that uses more than one Authentication Middleware and thus has more than one authentication scheme, the scheme that Blazor uses can be explicitly set in the endpoint configuration of `Startup.Configure`. The following example sets the Microsoft Entra ID scheme:
+For an app that uses more than one authentication middleware and thus has more than one authentication scheme, the scheme that Blazor uses can be explicitly set in the endpoint configuration of `Startup.Configure`. The following example sets the Microsoft Entra ID scheme:
```csharp
endpoints.MapBlazorHub().RequireAuthorization(
@@ -803,7 +803,7 @@ Use the service in a component to obtain the user:
Hello, @(UserService.GetUser().Identity?.Name ?? "world")!
```
-To set the user in middleware for MVC, Razor Pages, and in other ASP.NET Core scenarios, call `SetUser` on the `UserService` in custom middleware after the Authentication Middleware runs, or set the user with an implementation. The following example adopts the middleware approach.
+To set the user in middleware for MVC, Razor Pages, and in other ASP.NET Core scenarios, call `SetUser` on the `UserService` in custom middleware after the authentication middleware runs, or set the user with an implementation. The following example adopts the middleware approach.
`UserServiceMiddleware.cs`:
diff --git a/aspnetcore/blazor/security/index.md b/aspnetcore/blazor/security/index.md
index 4a402e761278..ab1b54d48c62 100644
--- a/aspnetcore/blazor/security/index.md
+++ b/aspnetcore/blazor/security/index.md
@@ -79,7 +79,7 @@ The Blazor project template:
Antiforgery *middleware* isn't automatically included in the request processing pipeline without explicitly calling .
-To explicitly add Antiforgery Middleware, call after the call to . If there are calls to and , the call to must go between them. A call to must be placed after calls to and .
+To explicitly add antiforgery middleware, call after the call to . If there are calls to and , the call to must go between them. A call to must be placed after calls to and .
Adding token-based antiforgery middleware doesn't replace the automatic header-based CSRF protection middleware. When an app calls , both defense mechanisms run for a form post:
diff --git a/aspnetcore/blazor/security/webassembly/hosted-with-identity-server.md b/aspnetcore/blazor/security/webassembly/hosted-with-identity-server.md
index 54c97ffed18f..91d14bc0df90 100644
--- a/aspnetcore/blazor/security/webassembly/hosted-with-identity-server.md
+++ b/aspnetcore/blazor/security/webassembly/hosted-with-identity-server.md
@@ -185,7 +185,7 @@ The following services are registered.
:::moniker range="< aspnetcore-7.0"
- * The Authentication Middleware is responsible for validating request credentials and setting the user on the request context:
+ * The authentication middleware is responsible for validating request credentials and setting the user on the request context:
```csharp
app.UseAuthentication();
@@ -193,7 +193,7 @@ The following services are registered.
:::moniker-end
- * Authorization Middleware enables authorization capabilities:
+ * Authorization iddleware enables authorization capabilities:
```csharp
app.UseAuthorization();
diff --git a/aspnetcore/blazor/tutorials/movie-database-app/part-1.md b/aspnetcore/blazor/tutorials/movie-database-app/part-1.md
index 2b44ef40c851..c9b3ed46a8d0 100644
--- a/aspnetcore/blazor/tutorials/movie-database-app/part-1.md
+++ b/aspnetcore/blazor/tutorials/movie-database-app/part-1.md
@@ -318,7 +318,7 @@ HTTPS Redirection Middleware () enforces antiforgery protection for form processing:
+Antiforgery iddleware () enforces antiforgery protection for form processing:
```csharp
app.UseAntiforgery();
@@ -336,7 +336,7 @@ app.MapStaticAssets();
:::moniker range="< aspnetcore-9.0"
-Static File Middleware () serves static files, such as images, scripts, and stylesheets from the `wwwroot` folder:
+Static file middleware () serves static files, such as images, scripts, and stylesheets from the `wwwroot` folder:
```csharp
app.UseStaticFiles();
diff --git a/aspnetcore/blazor/tutorials/signalr-blazor.md b/aspnetcore/blazor/tutorials/signalr-blazor.md
index 0def71316fc9..e93526194c56 100644
--- a/aspnetcore/blazor/tutorials/signalr-blazor.md
+++ b/aspnetcore/blazor/tutorials/signalr-blazor.md
@@ -201,7 +201,7 @@ using Microsoft.AspNetCore.ResponseCompression;
using BlazorSignalRApp.Hubs;
```
-Add SignalR and Response Compression Middleware services:
+Add SignalR and response compression middleware services:
```csharp
builder.Services.AddSignalR();
@@ -213,7 +213,7 @@ builder.Services.AddResponseCompression(opts =>
});
```
-Use Response Compression Middleware at the top of the processing pipeline's configuration. Place the following line of code immediately after the line that builds the app (`var app = builder.Build();`):
+Use response compression middleware at the top of the processing pipeline's configuration. Place the following line of code immediately after the line that builds the app (`var app = builder.Build();`):
```csharp
app.UseResponseCompression();
@@ -242,7 +242,7 @@ Add an entry to the `NavMenu` component to reach the chat page. In `Components/L
```
> [!NOTE]
-> Disable Response Compression Middleware in the `Development` environment when using [Hot Reload](xref:test/hot-reload). For more information, see .
+> Disable response compression middleware in the `Development` environment when using [Hot Reload](xref:test/hot-reload). For more information, see .
## Run the app
@@ -422,7 +422,7 @@ Add the namespace for the `ChatHub` class to the top of the file:
using BlazorWebAssemblySignalRApp.Server.Hubs;
```
-Add SignalR and Response Compression Middleware services:
+Add SignalR and response compression middleware services:
```csharp
builder.Services.AddSignalR();
@@ -433,7 +433,7 @@ builder.Services.AddResponseCompression(opts =>
});
```
-Use Response Compression Middleware at the top of the processing pipeline's configuration immediately after the line that builds the app:
+Use response compression middleware at the top of the processing pipeline's configuration immediately after the line that builds the app:
```csharp
app.UseResponseCompression();
@@ -457,7 +457,7 @@ Add the namespace for the `ChatHub` class to the top of the file:
using BlazorWebAssemblySignalRApp.Server.Hubs;
```
-Add SignalR and Response Compression Middleware services:
+Add SignalR and response compression middleware services:
```csharp
services.AddSignalR();
@@ -468,7 +468,7 @@ services.AddResponseCompression(opts =>
});
```
-Use Response Compression Middleware at the top of the processing pipeline's configuration:
+Use response compression middleware at the top of the processing pipeline's configuration:
```csharp
app.UseResponseCompression();
@@ -519,7 +519,7 @@ Replace the markup with the following code:
:::moniker range=">= aspnetcore-6.0 < aspnetcore-8.0"
> [!NOTE]
-> Disable Response Compression Middleware in the `Development` environment when using [Hot Reload](xref:test/hot-reload). For more information, see .
+> Disable response compression middleware in the `Development` environment when using [Hot Reload](xref:test/hot-reload). For more information, see .
:::moniker-end
diff --git a/aspnetcore/breaking-changes/5/static-files-csv-content-type-changed.md b/aspnetcore/breaking-changes/5/static-files-csv-content-type-changed.md
index 2a543de4945a..40c54ce91c11 100644
--- a/aspnetcore/breaking-changes/5/static-files-csv-content-type-changed.md
+++ b/aspnetcore/breaking-changes/5/static-files-csv-content-type-changed.md
@@ -7,7 +7,7 @@ ms.custom: https://github.com/aspnet/Announcements/issues/395
---
# Static files: CSV content type changed to standards-compliant
-In ASP.NET Core 5.0, the default `Content-Type` response header value that the [Static File Middleware](/aspnet/core/fundamentals/static-files) uses for *.csv* files has changed to the standards-compliant value `text/csv`.
+In ASP.NET Core 5.0, the default `Content-Type` response header value that the [static file middleware](/aspnet/core/fundamentals/static-files) uses for *.csv* files has changed to the standards-compliant value `text/csv`.
For discussion on this issue, see [dotnet/aspnetcore#17385](https://github.com/dotnet/AspNetCore/issues/17385).
diff --git a/aspnetcore/client-side/spa/includes/intro6-7.md b/aspnetcore/client-side/spa/includes/intro6-7.md
index cec06996a12d..1d6430869bc2 100644
--- a/aspnetcore/client-side/spa/includes/intro6-7.md
+++ b/aspnetcore/client-side/spa/includes/intro6-7.md
@@ -5,7 +5,7 @@
The Single Page Application (SPA) templates for [Angular](https://angular.dev/) and [React](https://reactjs.org/) offer the ability to develop Angular and React apps that are hosted inside a .NET backend server.
-At publish time, the files of the Angular and React app are copied to the `wwwroot` folder and are served via the [Static File Middleware](xref:fundamentals/static-files).
+At publish time, the files of the Angular and React app are copied to the `wwwroot` folder and are served via the [static file middleware](xref:fundamentals/static-files).
Rather than returning HTTP 404 (Not Found), a fallback route handles unknown requests to the backend and serves the `index.html` for the SPA.
diff --git a/aspnetcore/fundamentals/error-handling.md b/aspnetcore/fundamentals/error-handling.md
index df38116d56d0..76d8478bc53f 100644
--- a/aspnetcore/fundamentals/error-handling.md
+++ b/aspnetcore/fundamentals/error-handling.md
@@ -139,7 +139,7 @@ By default, an ASP.NET Core app doesn't provide a status code page for HTTP erro
:::code language="csharp" source="~/fundamentals/error-handling/samples/7.x/ErrorHandlingSample/Snippets/Program.cs" id="snippet_UseStatusCodePages" highlight="9":::
-Call `UseStatusCodePages` before request handling middleware. For example, call `UseStatusCodePages` before the Static File Middleware and the Endpoints Middleware.
+Call `UseStatusCodePages` before request handling middleware. For example, call `UseStatusCodePages` before the static file middleware and the Endpoints Middleware.
When `UseStatusCodePages` isn't used, navigating to a URL without an endpoint returns a browser-dependent error message indicating the endpoint can't be found. When `UseStatusCodePages` is called, the browser returns the following response:
diff --git a/aspnetcore/fundamentals/error-handling/includes/error-handling3-7.md b/aspnetcore/fundamentals/error-handling/includes/error-handling3-7.md
index deac48d06e00..a739ffad6b7e 100644
--- a/aspnetcore/fundamentals/error-handling/includes/error-handling3-7.md
+++ b/aspnetcore/fundamentals/error-handling/includes/error-handling3-7.md
@@ -84,7 +84,7 @@ By default, an ASP.NET Core app doesn't provide a status code page for HTTP erro
:::code language="csharp" source="~/fundamentals/error-handling/samples/7.x/ErrorHandlingSample/Snippets/Program.cs" id="snippet_UseStatusCodePages" highlight="9":::
-Call `UseStatusCodePages` before request handling middleware. For example, call `UseStatusCodePages` before the Static File Middleware and the Endpoints Middleware.
+Call `UseStatusCodePages` before request handling middleware. For example, call `UseStatusCodePages` before the static file middleware and the Endpoints Middleware.
When `UseStatusCodePages` isn't used, navigating to a URL without an endpoint returns a browser-dependent error message indicating the endpoint can't be found. When `UseStatusCodePages` is called, the browser returns the following response:
@@ -394,7 +394,7 @@ By default, an ASP.NET Core app doesn't provide a status code page for HTTP erro
:::code language="csharp" source="~/fundamentals/error-handling/samples/6.x/ErrorHandlingSample/Snippets/Program.cs" id="snippet_UseStatusCodePages" highlight="9":::
-Call `UseStatusCodePages` before request handling middleware. For example, call `UseStatusCodePages` before the Static File Middleware and the Endpoints Middleware.
+Call `UseStatusCodePages` before request handling middleware. For example, call `UseStatusCodePages` before the static file middleware and the Endpoints Middleware.
When `UseStatusCodePages` isn't used, navigating to a URL without an endpoint returns a browser-dependent error message indicating the endpoint can't be found. When `UseStatusCodePages` is called, the browser returns the following response:
@@ -620,7 +620,7 @@ By default, an ASP.NET Core app doesn't provide a status code page for HTTP erro
:::code language="csharp" source="~/fundamentals/error-handling/samples/5.x/ErrorHandlingSample/StartupUseStatusCodePages.cs" id="snippet" highlight="13":::
-Call `UseStatusCodePages` before request handling middleware. For example, call `UseStatusCodePages` before the Static File Middleware and the Endpoints Middleware.
+Call `UseStatusCodePages` before request handling middleware. For example, call `UseStatusCodePages` before the static file middleware and the Endpoints Middleware.
When `UseStatusCodePages` isn't used, navigating to a URL without an endpoint returns a browser-dependent error message indicating the endpoint can't be found. For example, navigating to `Home/Privacy2`. When `UseStatusCodePages` is called, the browser returns:
@@ -859,7 +859,7 @@ To enable default text-only handlers for common error status codes, call exposes the app's [content root](xref:fundamentals/index#content-root) and [web root](xref:fundamentals/index#web-root) as `IFileProvider` types.
-* [Static File Middleware](xref:fundamentals/static-files) uses File Providers to locate static files.
+* [Static file middleware](xref:fundamentals/static-files) uses File Providers to locate static files.
* [Razor](xref:mvc/views/razor) uses File Providers to locate pages and views.
* .NET tooling uses File Providers and glob patterns to specify which files should be published.
@@ -173,7 +173,7 @@ The following table provides common examples of glob patterns.
ASP.NET Core abstracts file system access through the use of File Providers. File Providers are used throughout the ASP.NET Core framework:
* exposes the app's [content root](xref:fundamentals/index#content-root) and [web root](xref:fundamentals/index#web-root) as `IFileProvider` types.
-* [Static File Middleware](xref:fundamentals/static-files) uses File Providers to locate static files.
+* [Static file middleware](xref:fundamentals/static-files) uses File Providers to locate static files.
* [Razor](xref:mvc/views/razor) uses File Providers to locate pages and views.
* .NET tooling uses File Providers and glob patterns to specify which files should be published.
diff --git a/aspnetcore/fundamentals/localization/includes/localization35.md b/aspnetcore/fundamentals/localization/includes/localization35.md
index badfa25b2a3e..4aceb69040ad 100644
--- a/aspnetcore/fundamentals/localization/includes/localization35.md
+++ b/aspnetcore/fundamentals/localization/includes/localization35.md
@@ -251,7 +251,7 @@ Localization is configured in the `Startup.ConfigureServices` method:
### Localization middleware
-The current culture on a request is set in the localization [Middleware](xref:fundamentals/middleware/index). The localization middleware is enabled in the `Startup.Configure` method. The localization middleware must be configured before any middleware that might check the request culture (for example, `app.UseMvcWithDefaultRoute()`). Localization Middleware must appear after Routing Middleware if using . For more information on middleware order, see .
+The current culture on a request is set in the localization [Middleware](xref:fundamentals/middleware/index). The localization middleware is enabled in the `Startup.Configure` method. The localization middleware must be configured before any middleware that might check the request culture (for example, `app.UseMvcWithDefaultRoute()`). Localization Middleware must appear after routing middleware if using . For more information on middleware order, see .
[!code-csharp[](~/fundamentals/localization/sample/3.x/Localization/Startup.cs?name=snippet2)]
diff --git a/aspnetcore/fundamentals/middleware/index.md b/aspnetcore/fundamentals/middleware/index.md
index e817daf8801b..1568711f0fed 100644
--- a/aspnetcore/fundamentals/middleware/index.md
+++ b/aspnetcore/fundamentals/middleware/index.md
@@ -124,7 +124,7 @@ In the app's console window when the app is run:
> :::no-loc text="Work that doesn't write to the response. (2)":::
> :::no-loc text="Work that doesn't write to the response. (1)":::
-*Short-circuiting* the request pipeline is often desirable because it avoids unnecessary work. For example, [Static File Middleware](xref:fundamentals/static-files) can act as a *terminal middleware* by processing a request for a static file and short-circuiting the rest of the pipeline. Middleware added to the pipeline before the terminal middleware still processes code after their `next.Invoke` statements. If you don't plan to call `next.Invoke` because your goal is to terminate the pipeline, use a [`Run` delegate](#run-delegate) instead of calling the extension method.
+*Short-circuiting* the request pipeline is often desirable because it avoids unnecessary work. For example, [static file middleware](xref:fundamentals/static-files) can act as a *terminal middleware* by processing a request for a static file and short-circuiting the rest of the pipeline. Middleware added to the pipeline before the terminal middleware still processes code after their `next.Invoke` statements. If you don't plan to call `next.Invoke` because your goal is to terminate the pipeline, use a [`Run` delegate](#run-delegate) instead of calling the extension method.
Don't call `next.Invoke` during or after the response is sent to the client. After an is started, changes result in an exception. For example, [setting headers or a response status code throw an exception](xref:fundamentals/best-practices#do-not-modify-the-status-code-or-headers-after-the-response-body-has-started) after the response starts. Writing to the response body after calling `next` may:
@@ -361,7 +361,7 @@ app.Use(async (context, next) =>
});
```
-When a delegate doesn't pass a request to the next delegate, it's called *short-circuiting the request pipeline*. Short-circuiting is often desirable because it avoids unnecessary work. For example, [Static File Middleware](xref:fundamentals/static-files) can act as a *terminal middleware* by processing a request for a static file and short-circuiting the rest of the pipeline. Middleware added to the pipeline before the middleware that terminates further processing still processes code after their `next.Invoke` statements. However, see the following warning about attempting to write to a response that has already been sent.
+When a delegate doesn't pass a request to the next delegate, it's called *short-circuiting the request pipeline*. Short-circuiting is often desirable because it avoids unnecessary work. For example, [static file middleware](xref:fundamentals/static-files) can act as a *terminal middleware* by processing a request for a static file and short-circuiting the rest of the pipeline. Middleware added to the pipeline before the middleware that terminates further processing still processes code after their `next.Invoke` statements. However, see the following warning about attempting to write to a response that has already been sent.
> [!WARNING]
> Don't call `next.Invoke` after the response has been sent to the client. Changes to after the response has started throw an exception. For example, [setting headers and a status code throw an exception](xref:fundamentals/best-practices#do-not-modify-the-status-code-or-headers-after-the-response-body-has-started). Writing to the response body after calling `next`:
@@ -555,14 +555,14 @@ The following examples demonstrate middleware order for common app scenarios. Ea
* Exception Handler Middleware () catches exceptions thrown in the following middlewares.
* HTTP Strict Transport Security Protocol (HSTS) Middleware () adds the `Strict-Transport-Security` header.
1. HTTPS Redirection Middleware () redirects HTTP requests to HTTPS.
-1. Static File Middleware (if required, ) returns static files and short-circuits further request processing.
+1. Static file middleware (if required, ) returns static files and short-circuits further request processing.
1. Cookie Policy Middleware () conforms the app to the EU General Data Protection Regulation (GDPR).
-1. Routing Middleware () to route requests.
-1. Authentication Middleware () attempts to authenticate the user before they're allowed access to secure resources.
-1. Authorization Middleware () authorizes a user to access secure resources.
-1. Antiforgery Middleware () adds antiforgery middleware to the pipeline must be placed after calls to and .
+1. Routing middleware () to route requests.
+1. Authentication middleware () attempts to authenticate the user before they're allowed access to secure resources.
+1. Authorization middleware () authorizes a user to access secure resources.
+1. Antiforgery iddleware () adds antiforgery middleware to the pipeline must be placed after calls to and .
1. Session Middleware (Razor Pages and MVC only, ) establishes and maintains session state. If the app uses session state, call Session Middleware after Cookie Policy Middleware and before Razor Pages/MVC Middleware.
-1. Endpoint Routing Middleware
+1. Endpoint routing middleware
* to add Razor component endpoints to the request pipeline.
* to add Razor Pages endpoints to the request pipeline.
* to add controller endpoints to the request pipeline.
@@ -627,10 +627,10 @@ app.Run();
In the preceding code:
-* CORS Middleware (), Authentication Middleware (), and Authorization Middleware () must appear in the order shown.
+* CORS Middleware (), authentication middleware (), and authorization middleware () must appear in the order shown.
* CORS Middleware () must appear before Response Caching Middleware () to add CORS headers on every request, including cached responses. For more information, see [It is not clear that UseCORS must come before UseResponseCaching (`dotnet/aspnetcore` #23218](https://github.com/dotnet/aspnetcore/issues/23218).
-* Request Localization Middleware () must appear before any middleware that might check the request culture, for example, Static File Middleware ().
-* Rate Limiting Middleware () must be called after Routing Middleware () when rate limiting endpoint-specific APIs are used. For example, if the [`[EnableRateLimiting]` attribute](xref:Microsoft.AspNetCore.RateLimiting.EnableRateLimitingAttribute) is used, Rate Limiting Middleware must be called after Routing Middleware. When calling only global limiters, Rate Limiting Middleware can be called before Routing Middleware.
+* Request Localization Middleware () must appear before any middleware that might check the request culture, for example, static file middleware ().
+* Rate Limiting Middleware () must be called after routing middleware () when rate limiting endpoint-specific APIs are used. For example, if the [`[EnableRateLimiting]` attribute](xref:Microsoft.AspNetCore.RateLimiting.EnableRateLimitingAttribute) is used, Rate Limiting Middleware must be called after routing middleware. When calling only global limiters, Rate Limiting Middleware can be called before routing middleware.
In some scenarios, middleware has different ordering. For example, caching and compression ordering depends on the app's specification. In the following order, CPU usage might be reduced by caching the compressed response, but the app might end up caching multiple representations of a resource using different compression algorithms, such as Gzip or Brotli:
@@ -641,7 +641,7 @@ app.UseResponseCompression();
Static assets are typically served early in the pipeline so that the app can short-circuit request processing to improve performance.
-Authentication doesn't short-circuit unauthenticated requests. Although Authentication Middleware authenticates requests, authorization occurs after the framework selects a Razor component in a Blazor Web App, a page in a Razor Pages app, or a controller and action in an MVC app.
+Authentication doesn't short-circuit unauthenticated requests. Although authentication middleware authenticates requests, authorization occurs after the framework selects a Razor component in a Blazor Web App, a page in a Razor Pages app, or a controller and action in an MVC app.
:::moniker-end
@@ -746,13 +746,13 @@ The following `Program.cs` code adds middleware components for common app scenar
* Exception Handler Middleware () catches exceptions thrown in the following middlewares.
* HTTP Strict Transport Security Protocol (HSTS) Middleware () adds the `Strict-Transport-Security` header.
1. HTTPS Redirection Middleware () redirects HTTP requests to HTTPS.
-1. Static File Middleware () returns static files and short-circuits further request processing.
+1. Static file middleware () returns static files and short-circuits further request processing.
1. Cookie Policy Middleware () conforms the app to the EU General Data Protection Regulation (GDPR) regulations.
-1. Routing Middleware () to route requests.
-1. Authentication Middleware () attempts to authenticate the user before they're allowed access to secure resources.
-1. Authorization Middleware () authorizes a user to access secure resources.
+1. Routing middleware () to route requests.
+1. Authentication middleware () attempts to authenticate the user before they're allowed access to secure resources.
+1. Authorization middleware () authorizes a user to access secure resources.
1. Session Middleware () establishes and maintains session state. If the app uses session state, call Session Middleware after Cookie Policy Middleware and before MVC Middleware.
-1. Endpoint Routing Middleware ( with ) to add Razor Pages endpoints to the request pipeline.
+1. Endpoint routing middleware ( with ) to add Razor Pages endpoints to the request pipeline.
```csharp
if (env.IsDevelopment())
@@ -779,14 +779,14 @@ In the preceding example code, each middleware extension method is exposed on is the first middleware component added to the pipeline. Therefore, the Exception Handler Middleware catches any exceptions that occur in later calls.
-Static File Middleware is called early in the pipeline so that it can handle requests and short-circuit without going through the remaining components. The Static File Middleware provides **no** authorization checks. Any files served by Static File Middleware, including those under *wwwroot*, are publicly available. For an approach to secure static files, see .
+Static file middleware is called early in the pipeline so that it can handle requests and short-circuit without going through the remaining components. The static file middleware provides **no** authorization checks. Any files served by static file middleware, including those under *wwwroot*, are publicly available. For an approach to secure static files, see .
-If the request isn't handled by the Static File Middleware, it's passed on to the Authentication Middleware (), which performs authentication. Authentication doesn't short-circuit unauthenticated requests. Although Authentication Middleware authenticates requests, authorization (and rejection) occurs only after MVC selects a specific Razor Page or MVC controller and action.
+If the request isn't handled by the static file middleware, it's passed on to the authentication middleware (), which performs authentication. Authentication doesn't short-circuit unauthenticated requests. Although authentication middleware authenticates requests, authorization (and rejection) occurs only after MVC selects a specific Razor Page or MVC controller and action.
-The following example demonstrates a middleware order where requests for static files are handled by Static File Middleware before Response Compression Middleware. Static files aren't compressed with this middleware order. The Razor Pages responses can be compressed.
+The following example demonstrates a middleware order where requests for static files are handled by static file middleware before response compression middleware. Static files aren't compressed with this middleware order. The Razor Pages responses can be compressed.
```csharp
-// Static files aren't compressed by Static File Middleware.
+// Static files aren't compressed by static file middleware.
app.UseStaticFiles();
app.UseRouting();
@@ -900,13 +900,13 @@ The following `Program.cs` code adds middleware components for common app scenar
* Exception Handler Middleware () catches exceptions thrown in the following middlewares.
* HTTP Strict Transport Security Protocol (HSTS) Middleware () adds the `Strict-Transport-Security` header.
1. HTTPS Redirection Middleware () redirects HTTP requests to HTTPS.
-1. Static File Middleware () returns static files and short-circuits further request processing.
+1. Static file middleware () returns static files and short-circuits further request processing.
1. Cookie Policy Middleware () conforms the app to the EU General Data Protection Regulation (GDPR) regulations.
-1. Routing Middleware () to route requests.
-1. Authentication Middleware () attempts to authenticate the user before they're allowed access to secure resources.
-1. Authorization Middleware () authorizes a user to access secure resources.
+1. Routing middleware () to route requests.
+1. Authentication middleware () attempts to authenticate the user before they're allowed access to secure resources.
+1. Authorization middleware () authorizes a user to access secure resources.
1. Session Middleware () establishes and maintains session state. If the app uses session state, call Session Middleware after Cookie Policy Middleware and before MVC Middleware.
-1. Endpoint Routing Middleware ( with ) to add Razor Pages endpoints to the request pipeline.
+1. Endpoint routing middleware (