Skip to content

Correct browser content negotiation formatter selection documentation #36586

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
HenryZhang-ZHY wants to merge 1 commit into
base: main
Choose a base branch
from
+5 −4
Open

Correct browser content negotiation formatter selection documentation #36586

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions aspnetcore/web-api/advanced/formatting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,12 @@
---
title: Format response data in ASP.NET Core Web API
ai-usage: ai-assisted
author: tdykstra
description: Learn how to format response data in ASP.NET Core Web API.
monikerRange: '>= aspnetcore-3.1'
ms.author: tdykstra
ms.custom: H1Hack27Feb2017
ms.date: 04/08/2022
ms.date: 01/07/2026
uid: web-api/advanced/formatting
---
# Format response data in ASP.NET Core Web API
Expand Down Expand Up @@ -97,7 +98,7 @@ If the Accept header contains `*/*`, the Header is ignored unless `RespectBrowse
Unlike typical API clients, web browsers supply `Accept` headers. Web browsers specify many formats, including wildcards. By default, when the framework detects that the request is coming from a browser:

* The `Accept` header is ignored.
* The content is returned in JSON, unless otherwise configured.
* The content is returned using the first registered output formatter that can handle the response type, unless otherwise configured.

This approach provides a more consistent experience across browsers when consuming APIs.

Expand Down Expand Up @@ -294,7 +295,7 @@ If the Accept header contains `*/*`, the Header is ignored unless `RespectBrowse
Unlike typical API clients, web browsers supply `Accept` headers. Web browsers specify many formats, including wildcards. By default, when the framework detects that the request is coming from a browser:

* The `Accept` header is ignored.
* The content is returned in JSON, unless otherwise configured.
* The content is returned using the first registered output formatter that can handle the response type, unless otherwise configured.

This approach provides a more consistent experience across browsers when consuming APIs.

Expand Down Expand Up @@ -529,7 +530,7 @@ If the Accept header contains `*/*`, the Header is ignored unless `RespectBrowse
Unlike typical API clients, web browsers supply `Accept` headers. Web browsers specify many formats, including wildcards. By default, when the framework detects that the request is coming from a browser:

* The `Accept` header is ignored.
* The content is returned in JSON, unless otherwise configured.
* The content is returned using the first registered output formatter that can handle the response type, unless otherwise configured.

This approach provides a more consistent experience across browsers when consuming APIs.

Expand Down