Skip to content

Commit

Permalink
Add section for handling unknown options/data.
Browse files Browse the repository at this point in the history
- adds text requiring implementations throw an error on receiving data, options, or option values not understood by the endpoint.
  • Loading branch information
wes-smith authored and msporny committed Jun 25, 2024
1 parent ff7b863 commit a230e09
Showing 1 changed file with 10 additions and 1 deletion.
11 changes: 10 additions & 1 deletion index.html
Original file line number Diff line number Diff line change
Expand Up @@ -686,7 +686,16 @@ <h3>Content Serialization</h3>
All entity bodies in requests and responses sent to or received from the API endpoints defined by this specification MUST be serialized as JSON and include the `Content-Type` header with a media type value of `application/json`.
</p>
</section>

<section>
<h3>Handling Unknown Options and Data</h3>
<p>
Many of the endpoints defined in the following sections receive data and options in request bodies.
</p>
<p>
Implementations MUST throw an error if an endpoint receives data, options, or option values that it
does not understand or know how to process.
</p>
</section>
<section>
<h3>API Component Overview</h3>
<p>
Expand Down

0 comments on commit a230e09

Please sign in to comment.