-
I suggest that we add "default responses" that can be defined as default response for All endpoints. This would avoid copy-paste for some common responses like:
429 Too Many Requests
405 Method Not A…
-
**Affects:** \6.0.11
When using Spring's validation and Open Telemetry (agent version 1.25.0) we are seeing the rejected values (personal information) on the event within our spans.
We have a …
-
@dlongley wrote:
I think we need a cleaner separation of cryptosuite verification and purpose verification. We should:
1. Find a proof that matches the expected purpose; if none is found, raise …
-
The following line causing 406 Error while using any subtype of ProblemDetail class.
```
// For ProblemDetail, fall back on RFC 7807 format
if (bestMediaType == null && elementType.toClass().…
-
Since this module adds support for JSON "problem" structure, as per RFC 7807:
https://www.rfc-editor.org/rfc/rfc7807
it would make sense to add a link on README to make it easier to find, by any…
-
**Description**
Hello,
I'm using API ¨Platform 3.1.x, and I'm using the SerializerContextBuilderInterface::createFromRequest method to add context used by Providers (mainly to avoid injecting sy…
-
**Problem description**
When attempting to access a session using the GET /sessions/{sessionId} endpoint, if you provide an invalid UUID as the sessionId parameter, the API will respond with an appro…
-
**Operating System**: Windows
**DocFX Version Used**: 2.59.0
**Template used**: default
**Steps to Reproduce**:
1. Create a default docset with `docfx init`.
2. Append the following to `i…
-
**API Platform version(s) affected**: 3.2.1
**Description**
I face a strange behavior.
After a migration from ApiPlatform 3.1.18 to 3.2.1, it seems that the response's body structure has chan…
-
The original example in https://www.rfc-editor.org/rfc/rfc7807#section-3 is more about a business problem than about an HTTP problem. It might be helpful to change the example to one that's more speci…