Skip to content

Commit b42163c

Browse files
committed
fix: small clarifications
Per @dgeb’s suggestions
1 parent e59ea8e commit b42163c

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

_format/1.1/index.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -2147,20 +2147,20 @@ when encountering unrecognized values.
21472147
If a profile does not define its own rules for handling unrecognized values,
21482148
the following rule applies by default:
21492149

2150-
1. If the unrecognized value occurs is the value of a profile-defined query
2151-
parameter, the server **MUST** fail the request and respond with a
2152-
`400 Bad Request` and an [error object][error objects] indicating the
2153-
problematic parameter.
2150+
1. If the value of a profile-defined query parameter is unrecognized, the
2151+
server **MUST** fail the request and respond with a `400 Bad Request` and
2152+
an [error object][error objects] indicating the problematic parameter.
21542153

2155-
2. Otherwise, if the unrecognized value is a JSON object, and the only thing
2156-
that makes it unrecognized is that it contains one or more keys that have
2157-
no meaning assigned to them (in the latest revision of the profile that the
2158-
application is aware of), then the application **MUST** simply ignore those
2159-
unknown keys and continue processing the profile.
2154+
2. Otherwise, if the unrecognized value is a JSON object in the
2155+
request/response document, and the only thing that makes it unrecognized
2156+
is that it contains one or more keys that have no meaning assigned to them
2157+
(in the latest revision of the profile that the application is aware of),
2158+
then the application **MUST** simply ignore those unknown keys and
2159+
continue processing the profile.
21602160

21612161
3. In all other cases, the application **MUST** assume that the profile has
21622162
been applied erroneously and **MUST** totally ignore the profile (i.e.,
2163-
process the document as if the profile were not there).
2163+
process the request as if the profile were not there).
21642164

21652165
In the case of our example [timestamps profile], it does not define its own
21662166
rules, so the above defaults would apply.

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy