We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prerequisites:
204 No Content
Content-Type: application/json
Steps to Reproduce:
POST http://host.tld/some-api HTTP/1.1 Content-Type: application/json {}
Actual behaviour:
The content type of response is application/json, while response body is not a valid json string
Expected behaviour:
Comments:
As per RFC 2616, the server can respond with both Content-Type header and empty body under 204 HTTP code. Please see these links for details: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.5 http://www.w3.org/Protocols/rfc2616/rfc2616-sec7.html#sec7.1
Content-Type
Suggested changes:
The text was updated successfully, but these errors were encountered:
Suppress response body validation for empty JSON response #598
8ca15af
@YBogomolov nice catch, I have fixed this issue and will publish it in the next release.
Sorry, something went wrong.
@YBogomolov you can verify this in the latest version 0.24.0
@Huachao It works as intended, thank you!
No branches or pull requests
Prerequisites:
204 No Content
code,Content-Type: application/json
headers and empty body.Steps to Reproduce:
Actual behaviour:
The content type of response is application/json, while response body is not a valid json string
.Expected behaviour:
Comments:
As per RFC 2616, the server can respond with both
Content-Type
header and empty body under 204 HTTP code. Please see these links for details:http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.5
http://www.w3.org/Protocols/rfc2616/rfc2616-sec7.html#sec7.1
Suggested changes:
The text was updated successfully, but these errors were encountered: