Skip to content

Clarify that server should response with 400 Bad Request in both cases #1616

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.

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

Merged
merged 1 commit into from
Apr 2, 2022

Conversation

jelhan
Copy link
Contributor

@jelhan jelhan commented Feb 23, 2022

This has been discussed in #1545. The change was already approved by two editors of the spec: @dgeb and @gabesullice But seems as no one has opened a PR yet.

Thanks a lot to @Relequestual for spotting this one!

Closes #1545

@jelhan jelhan added this to the v1.1 milestone Feb 23, 2022
@jelhan jelhan requested review from dgeb and gabesullice February 23, 2022 18:11
Copy link
Member

@dgeb dgeb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for addressing this, @jelhan!

@dgeb dgeb merged commit 9f47012 into json-api:gh-pages Apr 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Should this query parameter 400 response be OR as opposed to AND?
3 participants
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