Skip to content
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

Jump to bottom

Fix explanation on default settings for content negotiation in reference doc #27067

Merged
merged 1 commit into from Jul 12, 2021
Merged

Fix explanation on default settings for content negotiation in reference doc #27067

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.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 3 additions & 5 deletions src/docs/asciidoc/web/webmvc.adoc
View file
Open in desktop
Expand Up @@ -5366,12 +5366,10 @@ The following example shows how to achieve the same configuration in XML:
You can configure how Spring MVC determines the requested media types from the request
(for example, `Accept` header, URL path extension, query parameter, and others).

By default, the URL path extension is checked first -- with `json`, `xml`, `rss`, and `atom`
registered as known extensions (depending on classpath dependencies). The `Accept` header
is checked second.
By default, only the `Accept` header is checked.

Consider changing those defaults to `Accept` header only, and, if you must use URL-based
content type resolution, consider using the query parameter strategy over path extensions. See
If you must use URL-based content type resolution, consider using the query parameten
strategy over path extensions. See
<<mvc-ann-requestmapping-suffix-pattern-match>> and <<mvc-ann-requestmapping-rfd>> for
more details.

Expand Down