Merge branch 'main' into guardrex/blazor-preview-5

Author: guardrex

aspnetcore/fundamentals/map-static-files.md

@@ -2,15 +2,19 @@
 title: Map static files in ASP.NET Core
 author: rick-anderson
 description: Learn how to serve and secure mapped static files and configure static file hosting middleware behaviors in an ASP.NET Core web app.
-monikerRange: '>= aspnetcore-8.0'
+monikerRange: '>= aspnetcore-9.0'
 ms.author: riande
 ms.custom: mvc
 ms.date: 3/18/2025
 uid: fundamentals/map-static-files
 ---
 # Map static files in ASP.NET Core
 
-:::moniker range=">= aspnetcore-9.0"
+<!-- UPDATE 10.0 - Activate at GA
+
+[!INCLUDE[](~/includes/not-latest-version.md)]
+
+-->
 
 By [Rick Anderson](https://twitter.com/RickAndMSFT)
 
@@ -209,5 +213,3 @@ The following code updates `IWebHostEnvironment.WebRootPath` to a non developmen
 * [Introduction to ASP.NET Core](xref:index)
 * <xref:blazor/file-uploads>
 * <xref:blazor/file-downloads>
-
-:::moniker-end

aspnetcore/fundamentals/servers/kestrel/http3.md

@@ -27,18 +27,14 @@ uid: fundamentals/servers/kestrel/http3
 * Is the latest version of the Hypertext Transfer Protocol.
 * Builds on the strengths of `HTTP/2` while addressing some of its limitations, particularly in terms of performance, latency, reliability, and security.
 
-+---------------+-------------------------+-------------------------+
-| Feature | `HTTP/2` | `HTTP/3` |
-+---------------+-------------------------+-------------------------+
-| Transport | Uses [TCP](https://developer.mozilla.org/docs/Glossary/TCP) | Uses [QUIC](https://www.rfc-editor.org/rfc/rfc9000.html)  |
-| Layer | | |
-| Connection | Slower due to TCP + TLS | Faster with 0-RTT QUIC |
-| Setup | handshake | handshakes |
-| Head-of-Line | Affected by TCP-level | Eliminated with QUIC |
-| Blocking | blocking | stream multiplexing |
-| Encryption | TLS over TCP | TLS is built into QUIC |
-+---------------+-------------------------+-------------------------+
-
+| Feature      | `HTTP/2`                                                    | `HTTP/3`                                                 |
+|--------------|-------------------------------------------------------------|----------------------------------------------------------|
+| Transport    | Uses [TCP](https://developer.mozilla.org/docs/Glossary/TCP) | Uses [QUIC](https://www.rfc-editor.org/rfc/rfc9000.html) |
+| Connection   | Slower due to TCP + TLS                                     | Faster with 0-RTT QUIC                                   |
+| Setup        | handshake                                                   | handshakes                                               |
+| Head-of-Line | Affected by TCP-level                                       | Eliminated with QUIC                                     |
+| Blocking     | blocking                                                    | stream multiplexing                                      |
+| Encryption   | TLS over TCP                                                | TLS is built into QUIC                                   |
 
 The key differences from `HTTP/2` to `HTTP/3` are:
 

aspnetcore/fundamentals/servers/yarp/transforms-request.md

@@ -491,7 +491,7 @@ Disable default headers:
 transformBuilderContext.UseDefaultForwarders = false;
 ```
 
-When the proxy connects to the destination server, the connection is indepenent from the one the client made to the proxy. The destination server likely needs original connection information for security checks and to properly generate absolute URIs for links and redirects. To enable information about the client connection to be passed to the destination a set of extra headers can be added. Until the `Forwarded` standard was created, a common solution is to use `X-Forwarded-*` headers. There is no official standard that defines the `X-Forwarded-*` headers and implementations vary, check your destination server for support.
+When the proxy connects to the destination server, the connection is independent from the one the client made to the proxy. The destination server likely needs original connection information for security checks and to properly generate absolute URIs for links and redirects. To enable information about the client connection to be passed to the destination a set of extra headers can be added. Until the `Forwarded` standard was created, a common solution is to use `X-Forwarded-*` headers. There is no official standard that defines the `X-Forwarded-*` headers and implementations vary, check your destination server for support.
 
 This transform is enabled by default even if not specified in the route config.
 
@@ -599,4 +599,4 @@ As the inbound and outbound connections are independent, there needs to be a way
 
 Servers do minimal validation on the incoming client certificate by default. The certificate should be validated either in the proxy or the destination, see the [client certificate auth](/aspnet/core/security/authentication/certauth) docs for details.
 
-This transform will only apply if the client certificate is already present on the connection. See the [optional certs doc](/aspnet/core/security/authentication/certauth#optional-client-certificates) if it needs to be requested from the client on a per-route basis.
+This transform will only apply if the client certificate is already present on the connection. See the [optional certs doc](/aspnet/core/security/authentication/certauth#optional-client-certificates) if it needs to be requested from the client on a per-route basis.

aspnetcore/grpc/grpcweb/sample/8.x/GrpcGreeter/Program.cs

@@ -33,7 +33,7 @@
 
 app.UseGrpcWeb(new GrpcWebOptions { DefaultEnabled = true });
 
-app.MapGrpcService<GreeterService>().EnableGrpcWeb();
+app.MapGrpcService<GreeterService>();
 app.MapGet("/", () => "All gRPC service are supported by default in this example, and are callable from browser apps using the gRPC-Web protocol");
 
 app.Run();

aspnetcore/release-notes/aspnetcore-10.0.md

@@ -1,8 +1,8 @@
 ---
 title: What's new in ASP.NET Core in .NET 10
-author: rick-anderson
+author: wadepickett
 description: Learn about the new features in ASP.NET Core in .NET 10.
-ms.author: riande
+ms.author: wpickett
 ms.custom: mvc
 ms.date: 6/9/2025
 uid: aspnetcore-10
@@ -13,8 +13,6 @@ This article highlights the most significant changes in ASP.NET Core in .NET 10
 
 This article will be updated as new preview releases are made available. For breaking changes, see [Breaking changes in .NET](/dotnet/core/compatibility/breaking-changes).
 
-<!-- New content should be added to ~/aspnetcore-9/includes/newFeatureName.md files. This will help prevent merge conflicts in this file. -->
-
 ## Blazor
 
 This section describes new features for Blazor.
@@ -61,7 +59,7 @@ This section describes new features for OpenAPI.
 
 [!INCLUDE[](~/release-notes/aspnetcore-10/includes/OpenApiSchemasInTransformers.md)]
 
-[!INCLUDE[](~/release-notes/aspnetcore-10/includes/OpenApiNetUpdatePrev17.md)]
+[!INCLUDE[](~/release-notes/aspnetcore-10/includes/OpenApiNetUpdatePrev.md)]
 
 ### Authentication and authorization
 
@@ -90,8 +88,9 @@ For more information, see [ASP.NET Core Authorization and Authentication metrics
 
 This section describes miscellaneous new features in .NET 10.
 
-[!INCLUDE[](~/release-notes/aspnetcore-10/includes/testAppsTopLevel.md)]
+[!INCLUDE[](~/release-notes/aspnetcore-10/includes/httpsys.md)]
 
+[!INCLUDE[](~/release-notes/aspnetcore-10/includes/testAppsTopLevel.md)]
 
 [!INCLUDE[](~/release-notes/aspnetcore-10/includes/jsonPatch.md)]
 
@@ -116,3 +115,5 @@ if (RedirectHttpResult.IsLocalUrl(url))
 Thank you [@martincostello](https://github.com/martincostello) for this contribution!
 
 ## Related content
+
+<xref:fundamentals/servers/httpsys>

aspnetcore/release-notes/aspnetcore-10/includes/OpenApiNetUpdatePrev.md

@@ -0,0 +1,8 @@
+### OpenAPI.NET updated to Preview.18
+
+The OpenAPI.NET library used in ASP.NET Core OpenAPI document generation was upgraded to [v2.0.0-preview18](https://www.nuget.org/packages/Microsoft.OpenApi/2.0.0-preview.18). The v2.0.0-preview18 version improves compatibility with the updated library version.
+
+The previous v2.0.0-preview17 version included a number of bug fixes and improvements and also introduced some breaking changes. The breaking changes should only affect users that use document, operation, or schema transformers. Breaking changes in this version that may affect developers include the following:
+
+* [Ephemeral object properties are now in Metadata](https://github.com/microsoft/OpenAPI.NET/blob/main/docs/upgrade-guide-2.md#ephemeral-object-properties-are-now-in-metadata)
+* [Use HTTP Method Object Instead of Enum](https://github.com/microsoft/OpenAPI.NET/blob/main/docs/upgrade-guide-2.md#use-http-method-object-instead-of-enum)

aspnetcore/release-notes/aspnetcore-10/includes/OpenApiNetUpdatePrev17.md

@@ -31,3 +31,6 @@ app.MapPost("/products",
         => TypedResults.Ok(productId))
     .DisableValidation();
 ```
+
+> [!NOTE]
+> Several small improvements and fixes have been made to the Minimal APIs validation generator introduced in ASP.NET Core for .NET 10. To support future enhancements, the underlying validation resolver APIs are now marked as experimental. The top-level `AddValidation` APIs and the built-in validation filter remain stable and non-experimental.

aspnetcore/release-notes/aspnetcore-10/includes/ValidationSupportMinAPI.md

@@ -0,0 +1,17 @@
+### Customizable security descriptors for HTTP.sys
+<!--PR: https://github.com/dotnet/aspnetcore/pull/61325-->
+
+You can now specify a custom security descriptor for HTTP.sys request queues. The new [RequestQueueSecurityDescriptor](https://source.dot.net/#Microsoft.AspNetCore.Server.HttpSys/HttpSysOptions.cs,a556950881fd2d87) property on <xref:Microsoft.AspNetCore.Server.HttpSys.HttpSysOptions> enables more granular control over access rights for the request queue. This granular control lets you tailor security to your application's needs.
+
+#### What you can do with the new property
+
+A *request queue* in HTTP.sys is a kernel-level structure that temporarily stores incoming HTTP requests until your application is ready to process them. By customizing the security descriptor, you can allow or deny specific users or groups access to the request queue. This is useful in scenarios where you want to restrict or delegate HTTP.sys request handling at the operating system level.
+
+#### How to use the new property
+
+The `RequestQueueSecurityDescriptor` property applies only when creating a new request queue. The property doesn't affect existing request queues. To use this property, set it to a <xref:System.Security.AccessControl.GenericSecurityDescriptor> instance when configuring your HTTP.sys server.
+
+For example, the following code allows all authenticated users but denies guests:
+[!code-csharp[](~/release-notes/aspnetcore-10/samples/HttpSysConfig/Program.cs)]
+
+For more information, see <xref:fundamentals/servers/httpsys>.

aspnetcore/release-notes/aspnetcore-10/includes/httpsys.md

@@ -0,0 +1,33 @@
+using System.Security.AccessControl;
+using System.Security.Principal;
+using Microsoft.AspNetCore.Server.HttpSys;
+
+// Create a new security descriptor
+var securityDescriptor = new CommonSecurityDescriptor(isContainer: false, isDS: false, sddlForm: string.Empty);
+
+// Create a discretionary access control list (DACL)
+var dacl = new DiscretionaryAcl(isContainer: false, isDS: false, capacity: 2);
+dacl.AddAccess(
+    AccessControlType.Allow,
+    new SecurityIdentifier(WellKnownSidType.BuiltinUsersSid, null),
+    -1,
+    InheritanceFlags.None,
+    PropagationFlags.None
+);
+dacl.AddAccess(
+    AccessControlType.Deny,
+    new SecurityIdentifier(WellKnownSidType.BuiltinGuestsSid, null),
+    -1,
+    InheritanceFlags.None,
+    PropagationFlags.None
+);
+
+// Assign the DACL to the security descriptor
+securityDescriptor.DiscretionaryAcl = dacl;
+
+// Configure HTTP.sys options
+var builder = WebApplication.CreateBuilder();
+builder.WebHost.UseHttpSys(options =>
+{
+    options.RequestQueueSecurityDescriptor = securityDescriptor;
+});