Skip to content

"tooMany" error message should give response status 400, not 413#100

Open
fflorent wants to merge 1 commit intoscimmyjs:mainfrom
fflorent:fix-tooMany
Open

"tooMany" error message should give response status 400, not 413#100
fflorent wants to merge 1 commit intoscimmyjs:mainfrom
fflorent:fix-tooMany

Conversation

@fflorent
Copy link
Copy Markdown

@fflorent fflorent commented Mar 7, 2026

The RFC 7644 states this:

If a SCIM service provider determines that too many results would be
returned (e.g., because a client queried a resource type endpoint or
the server base URI), the server SHALL reject the request by
returning an HTTP response with HTTP status code 400 (Bad Request)
and JSON attribute "scimType" set to "tooMany" (see Table 9).

Also 413 (Content Too Large) should be returned when the request has a too large payload, but does not relate to the response. Quoting RFC 9110 (https://datatracker.ietf.org/doc/html/rfc9110#name-413-content-too-large):

The 413 (Content Too Large) status code indicates that the server is
refusing to process a request because the request content is larger
than the server is willing or able to process.

The RFC 7644 states this:

   If a SCIM service provider determines that too many results would be
   returned (e.g., because a client queried a resource type endpoint or
   the server base URI), the server SHALL reject the request by
   returning an HTTP response with HTTP status code 400 (Bad Request)
   and JSON attribute "scimType" set to "tooMany" (see Table 9).

Also 413 (Content Too Large) should be returned when the request has a
too large payload, but does not relate to the response. Quoting RFC
9110 (<https://datatracker.ietf.org/doc/html/rfc9110#name-413-content-too-large>):

  The 413 (Content Too Large) status code indicates that the server is
  refusing to process a request because the request content is larger
  than the server is willing or able to process.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant