Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

When I am doing a fast test of various APIs for GET operations, I like to use a browser.

It seems that Chromium (both Edge and Chrome) has introduced the in title referenced header: https://wicg.github.io/webpackage/draft-yasskin-http-origin-signed-responses.html#section-8.6

This "throws" a 400/InvalidApiVersion when encountered and my API is set to use v for version parameter name.

Describe the solution you'd like

If possible, tweak MediaTypeApiVersionReader to be aware of this IANA defined header (application/signed-exchange) and read pass it (eg. skip it).

Additional context

https://github.com/dotnet/aspnet-api-versioning/blob/main/src/Common/src/Common/MediaTypeApiVersionReader.cs