Forum Discussion

detvetdu's avatar
detvetdu
Occasional Contributor
8 years ago
Solved

Assertion fail for valid HTTP code 204

In earlier versions than 1.9 of ReadyApi the assertion for HTTP 204 worked fine.  In this version I get failed assertion for HTTP code 204 when i response header returns "Content-Length: 0" with er...
AV's avatar
AV
SmartBear Alumni (Retired)
8 years ago

Hello, detvetdu,

thanks for reaching out us, this assertion behaviour was changed basing on customer's request. Here is some additional information about that:

 

According to section 3.3.2 of RFC 7230 (Proposed Standard, RFC 7230):

 

A server MUST NOT send a Content-Length header field in any response
with a status code of 1xx (Informational) or 204 (No Content). A
server MUST NOT send a Content-Length header field in any 2xx
(Successful) response to a CONNECT request (Section 4.3.6 of
[RFC7231]).

  • detvetdu's avatar
    detvetdu
    Occasional Contributor
    8 years ago

    If you add extra check in the assertion for http codes you add assertions for standard as well.

    Shouldn't that be an assertion for the header is following the http standard?

     

    I agree that http 204 should not contain content length header. But the assertions for valid http codes do to much check with this new feature.