You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This should allow problem details responses to be correctly emitted in the case where the incoming media type is more specific than the known media types, as is the case when an API version is included in the header, e.g. application/json; v=1.0.
Expected Behavior
No response
Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Describe the bug
As diagnosed here, it has been determined that the conditional logic inside the
CanWrite
method ofRfc7231ProblemDetailsWriter
should be as follows:This should allow problem details responses to be correctly emitted in the case where the incoming media type is more specific than the known media types, as is the case when an API version is included in the header, e.g.
application/json; v=1.0
.Expected Behavior
No response
Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: