-
Notifications
You must be signed in to change notification settings - Fork 152
REST Security Error handling
While handling errors on the server side for your REST APIs:
- you MUST NEVER send stack traces to API clients
- doing so provides too much insight into the inner workings of your application, potentially helping attackers
- you MUST NEVER send information about software and software versions as that could ease the work of an attacker
- doing so provides too much insight into what is used to run your application. For example, if an attacker can find out that your application runs under Tomcat 8.5.1, then he can easily check all security flaws that your application server is not protected against and use these to attack your application and the underlying infrastructure
This project is distributed under the terms of the EUPL FOSS license
REST Resources Design Workflow
REST Resources Single items and collections
REST Resources Many to many Relations
REST Resources Relations expansion
HTTP Status Codes Success (2xx)
HTTP Status Codes Redirection (3xx)
HTTP Status Codes Client Error (4xx)
HTTP Status Codes Server Error (5xx)
Pagination Out of range/bounds
Long-running Operations Example
Concurrency vs Delete operation
Caching and conditional requests About
Caching and conditional requests Rules
Caching and conditional requests HTTP headers
Error handling Example with a single error
Error handling Example with multiple errors
Error handling Example with parameters
Error handling Example with additional metadata
Bulk operations HTTP status codes
Bulk operations Resources naming convention
Bulk operations Creation example
Bulk operations Update example
Bulk operations Create and update example
File upload Simple file upload
File upload Simple file upload example
File upload Complex file upload
File upload Complex file upload example
REST Security General recommendations
REST Security Insecure direct object references