AdditionalRequestHeaders

aspnetcore/fundamentals/w3c-logger/index.md

@@ -102,7 +102,7 @@ By default, W3CLogger logs common properties such as path, status-code, date, ti
 
 To configure the W3CLogger middleware, call <xref:Microsoft.Extensions.DependencyInjection.HttpLoggingServicesExtensions.AddW3CLogging%2A> in `Program.cs`:
 
-:::code language="csharp" source="samples/6.x/Program.cs" id="snippet_AddW3CLogging" highlight="3":::
+:::code language="csharp" source="samples/7.x/Program.cs" id="snippet_AddW3CLogging" highlight="3":::
 
 ### `LoggingFields`
 

aspnetcore/fundamentals/w3c-logger/samples/7.x/Program.cs

@@ -0,0 +1,35 @@
+using System;
+using System.Linq;
+using Microsoft.AspNetCore.Builder;
+using Microsoft.AspNetCore.HttpLogging;
+using Microsoft.Extensions.DependencyInjection;
+
+// <snippet_AddW3CLogging>
+var builder = WebApplication.CreateBuilder(args);
+
+builder.Services.AddW3CLogging(logging =>
+{
+    // Log all W3C fields
+    logging.LoggingFields = W3CLoggingFields.All;
+
+    logging.AdditionalRequestHeaders.Add("x-forwarded-for");
+    logging.AdditionalRequestHeaders.Add("x-client-ssl-protocol");
+    logging.FileSizeLimit = 5 * 1024 * 1024;
+    logging.RetainedFileCountLimit = 2;
+    logging.FileName = "MyLogFile";
+    logging.LogDirectory = @"C:\logs";
+    logging.FlushInterval = TimeSpan.FromSeconds(2);
+});
+// </snippet_AddW3CLogging>
+
+// <snippet_UseW3CLogging>
+var app = builder.Build();
+
+app.UseW3CLogging();
+
+app.UseRouting();
+// </snippet_UseW3CLogging>
+
+app.MapGet("/", () => "Hello World!");
+
+app.Run();

aspnetcore/fundamentals/w3c-logger/samples/7.x/W3CLoggerSample.csproj

@@ -0,0 +1,8 @@
+<Project Sdk="Microsoft.NET.Sdk.Web">
+
+  <PropertyGroup>
+    <TargetFramework>net7.0</TargetFramework>
+    <RootNamespace>W3CLoggerSample</RootNamespace>
+  </PropertyGroup>
+
+</Project>

aspnetcore/release-notes/aspnetcore-7.0.md

@@ -4,7 +4,7 @@ author: rick-anderson
 description: Learn about the new features in ASP.NET Core 7.0.
 ms.author: riande
 ms.custom: mvc
-ms.date: 08/09/2022
+ms.date: 08/15/2022
 uid: aspnetcore-7
 ---
 # What's new in ASP.NET Core 7.0 preview
@@ -29,7 +29,7 @@ The [`IParsable<TSelf>.TryParse`](/dotnet/api/system.iparsable-1.tryparse#system
 
 ### Parameter binding with DI in API controllers
 
-Parameter binding for API controller actions binds parameters through [dependency injection](xref:fundamentals/dependency-injection) when the type is configured as a service. This means it’s no longer required to explicitly apply the [`[FromServices]`](xref:Microsoft.AspNetCore.Mvc.FromServicesAttribute) attribute to a parameter. In the following code, both actions return the time:
+Parameter binding for API controller actions binds parameters through [dependency injection](xref:fundamentals/dependency-injection) when the type is configured as a service. This means it's no longer required to explicitly apply the [`[FromServices]`](xref:Microsoft.AspNetCore.Mvc.FromServicesAttribute) attribute to a parameter. In the following code, both actions return the time:
 
 [!code-csharp[](~/release-notes/aspnetcore-7/samples/ApiController/Controllers/MyController.cs?name=snippet)]
 
@@ -109,7 +109,7 @@ The following code shows the complete `Program.cs` file:
 Limitations when binding request body to `Stream` or `PipeReader`:
 
 * When reading data, the `Stream` is the same object as `HttpRequest.Body`.
-* The request body isn’t buffered by default. After the body is read, it’s not rewindable. The stream can't be read multiple times.
+* The request body isn't buffered by default. After the body is read, it's not rewindable. The stream can't be read multiple times.
 * The `Stream` and `PipeReader` aren't usable outside of the minimal action handler as the underlying buffers will be disposed or reused.
 
 ### New Results.Stream overloads
@@ -122,7 +122,7 @@ For more information, see [Stream examples](xref:fundamentals/minimal-apis?view=
 
 ### Typed results for minimal APIs
 
-In .NET 6, the <xref:Microsoft.AspNetCore.Http.IResult> interface was introduced to represent values returned from minimal APIs that don’t utilize the implicit support for JSON serializing the returned object to the HTTP response. The static [Results](/dotnet/api/microsoft.aspnetcore.http.results) class is used to create varying `IResult` objects that represent different types of responses. For example, setting the response status code or redirecting to another URL. The `IResult` implementing framework types returned from these methods were internal however, making it difficult to verify the specific `IResult` type being returned from methods in a unit test.
+In .NET 6, the <xref:Microsoft.AspNetCore.Http.IResult> interface was introduced to represent values returned from minimal APIs that don't utilize the implicit support for JSON serializing the returned object to the HTTP response. The static [Results](/dotnet/api/microsoft.aspnetcore.http.results) class is used to create varying `IResult` objects that represent different types of responses. For example, setting the response status code or redirecting to another URL. The `IResult` implementing framework types returned from these methods were internal however, making it difficult to verify the specific `IResult` type being returned from methods in a unit test.
 
 In .NET 7 the types implementing `IResult` are public, allowing for type assertions when testing. For example:
 
@@ -209,15 +209,15 @@ For more information, see [Shadow copying in IIS](xref:host-and-deploy/iis/advan
 
 The console output from dotnet watch has been improved to better align with the logging of ASP.NET Core and to stand out with 😮emojis😍.
 
-Here’s an example of what the new output looks like:
+Here's an example of what the new output looks like:
 
 ![output for dotnet watch](~/release-notes/aspnetcore-7/static/dnwatch.png)
 
 See [this GitHub pull request](https://github.com/dotnet/sdk/pull/23318) for more information.
 
 ### Configure dotnet watch to always restart for rude edits
 
-Rude edits are edits that  can’t be hot reloaded. To configure dotnet watch to always restart without a prompt for rude edits, set the `DOTNET_WATCH_RESTART_ON_RUDE_EDIT` environment variable to `true`.
+Rude edits are edits that  can't be hot reloaded. To configure dotnet watch to always restart without a prompt for rude edits, set the `DOTNET_WATCH_RESTART_ON_RUDE_EDIT` environment variable to `true`.
 
 ### Developer exception page dark mode
 
@@ -249,4 +249,18 @@ The Angular project template has been updated to Angular 14. The React project t
 
 ### Manage JSON Web Tokens in development with dotnet user-jwts
 
-The new `dotnet user-jwts` command line tool can create and manage app specific local [JSON Web Tokens](https://jwt.io/introduction) (JWTs). For more information, see [Manage JSON Web Tokens in development with dotnet user-jwts](xref:security/authentication/jwt?view=aspnetcore-7.0&preserve-view=true).
+The new `dotnet user-jwts` command line tool can create and manage app specific local [JSON Web Tokens](https://jwt.io/introduction) (JWTs). For more information, see [Manage JSON Web Tokens in development with dotnet user-jwts](xref:security/authentication/jwt?view=aspnetcore-7.0&preserve-view=true).
+
+### Support for additional request headers in W3CLogger
+
+You can now specify additional request headers to log when using the W3C logger by calling `AdditionalRequestHeaders()` on <xref:Microsoft.AspNetCore.HttpLogging.W3CLoggerOptions>:
+
+```csharp
+services.AddW3CLogging(logging =>
+{
+    logging.AdditionalRequestHeaders.Add("x-forwarded-for");
+    logging.AdditionalRequestHeaders.Add("x-client-ssl-protocol");
+});
+```
+
+For more information,see [W3CLogger options](xref:fundamentals/w3c-logger/index#w3clogger-options-1).