Removing experimental attribute from Http logging middleware

[mariamgerges]

Microsoft Reviewers: Open in CodeFlow

[mariamgerges]

@Tratcher @geeknoid these APIs were introduced in this PR and I'm not sure if they went through API review or not since this change was 3 years ago. Is it okay to remove the experimental attribute or we should go through API review first?

[Copilot]

Pull request overview

This PR removes the [Experimental] attribute from the HTTP logging middleware APIs in Microsoft.AspNetCore.Diagnostics.Middleware, promoting them from experimental to stable. The affected types are HttpLoggingServiceCollectionExtensions, IHttpLogEnricher, LoggingRedactionOptions, and the HeadersDataClasses property on RequestHeadersLogEnricherOptions.

Changes:

• Remove [Experimental] attribute (and associated DiagnosticIds usings) from HttpLoggingServiceCollectionExtensions, IHttpLogEnricher, LoggingRedactionOptions, and RequestHeadersLogEnricherOptions.HeadersDataClasses

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
HttpLoggingServiceCollectionExtensions.cs	Removes [Experimental] from the extension methods class
IHttpLogEnricher.cs	Removes [Experimental] from the enricher interface
LoggingRedactionOptions.cs	Removes [Experimental] from the redaction options class
RequestHeadersLogEnricherOptions.cs	Removes [Experimental] from the HeadersDataClasses property

[evgenyfedorov2]

for awareness - we are removing the Experimental attribute because the API was reviewed in bulk as part of the initial .NET 8 migration and the API became stable but later the attribute was unnecessarily added again.