No message in body for non-existent endpoint
See original GitHub issueSteps to reproduce:
- Send request to endpoint not listed in
SCIMEndpoints
. - Get response with 404 status code without body.
Expected result: Standard body with json should be returned in case of 4xx errors (according to RFC-7644, 3.12 HTTP Status and Error Response Handling)
{
"schemas": [
"urn:ietf:params:scim:api:messages:2.0:Error"
],
"status": "404",
"scimType": "unknown",
"detail": "some text"
}
Issue Analytics
- State:
- Created 7 months ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Getting "No message available" error with Spring Boot ...
So for nonexistent URL I've got 404 which is fair with "No message available" which is strange. Share.
Read more >When to use HTTP status code 404 in an API
If no data with such an ID exists, a 404 HTTP response is perfectly appropriate. Of course, the response body should, in any...
Read more >Troubleshooting Error Messages
This type of error message occurs when a required field for the requested endpoint was not properly specified. Below you will find common...
Read more >API calls and HTTP Status codes
What about a request for a non existent protected-vader.jpg file? It will first ask for credentials (that's a 401 code) and if the ......
Read more >Queue not found · Issue #2612 · localstack ...
As for API calls, these are PurgeQueueRequest, SendMessageRequest, and ReceiveMessageRequest. Error Message: Amazon.SQS.AmazonSQSException : The ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Indeed the
DefaultController
was not complete. The controller has been updated in the branchrelease\v3.0.2
, and the issue is fixedMy bad… the issue is fixed in the branch “release/v3.0.3”. The following changes have been made: