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

Add section for handling unknown options/data. #394

Merged
merged 1 commit into from
Jun 25, 2024
Merged

Add section for handling unknown options/data. #394

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
11 changes: 10 additions & 1 deletion index.html
View file
Open in desktop
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