This specification defines the HTTP QUERY method, providing a safe and idempotent way to perform complex server-side queries using request bodies rather than URI parameters. It fills the gap between GET and POST by allowing large or sensitive query data while remaining cacheable and suitable for automatic retries.
Main topics include:
* Safe and idempotent semantics similar to GET but with body support.
* Mechanisms for assigning URIs to query results via Location and Content-Location headers.
* Introduction of the Accept-Query header field for media type negotiation.
* Guidance on caching strategies involving request content in cache keys.
Main topics include:
* Safe and idempotent semantics similar to GET but with body support.
* Mechanisms for assigning URIs to query results via Location and Content-Location headers.
* Introduction of the Accept-Query header field for media type negotiation.
* Guidance on caching strategies involving request content in cache keys.
RFC 9457 defines a standardized format for communicating error details in HTTP API responses, known as "problem details."
- Supersedes RFC 7807,
- Core fields include 'type', 'title', 'detail' and 'instance'.
- Generally paired with 4xx/5xx HTTP status codes.
- Content types `application/problem+xml`, `application/problem+json`
Example:
```
{
"type": "https://example.com/probs/invalid-input",
"title": "Invalid Input",
"status": 400,
"detail": "The provided 'age' value must be a positive integer.",
"instance": "/users/123",
"age": -5
}
```
- Supersedes RFC 7807,
- Core fields include 'type', 'title', 'detail' and 'instance'.
- Generally paired with 4xx/5xx HTTP status codes.
- Content types `application/problem+xml`, `application/problem+json`
Example:
```
{
"type": "https://example.com/probs/invalid-input",
"title": "Invalid Input",
"status": 400,
"detail": "The provided 'age' value must be a positive integer.",
"instance": "/users/123",
"age": -5
}
```
