cancel
Showing results for 
Search instead for 
Did you mean: 

HTTP/1.1 204 No Content - Assertion is failing for valid HTTP status code 204. please advise.

SOLVED
Highlighted
New Contributor

HTTP/1.1 204 No Content - Assertion is failing for valid HTTP status code 204. please advise.

Below Raw response

 

HTTP/1.1 204 No Content
Content-Length: 0

 

The assertion passed for free version of SoapUI.

It is failing for ReadyAPI.

 

1 ACCEPTED SOLUTION

Accepted Solutions
Moderator

Re: HTTP/1.1 204 No Content - Assertion is failing for valid HTTP status code 204. please advise.

This should be fixed in the maintenance build of Ready! API 1.9:

https://support.smartbear.com/downloads/readyapi/nightly-builds/

 

But just FYI, a server that returns 204 with Content-Length is not RFC-compliant. RFC 7230 section 3.2.2 states:

> A server MUST NOT send a Content-Length header field in any response with a status code of 1xx (Informational) or 204 (No Content).


Helen Kosova
SmartBear Documentation Team Lead
________________________
Did my reply answer your question? Give Kudos or Accept it as a Solution to help others. ⬇️⬇️⬇️

View solution in original post

1 REPLY 1
Moderator

Re: HTTP/1.1 204 No Content - Assertion is failing for valid HTTP status code 204. please advise.

This should be fixed in the maintenance build of Ready! API 1.9:

https://support.smartbear.com/downloads/readyapi/nightly-builds/

 

But just FYI, a server that returns 204 with Content-Length is not RFC-compliant. RFC 7230 section 3.2.2 states:

> A server MUST NOT send a Content-Length header field in any response with a status code of 1xx (Informational) or 204 (No Content).


Helen Kosova
SmartBear Documentation Team Lead
________________________
Did my reply answer your question? Give Kudos or Accept it as a Solution to help others. ⬇️⬇️⬇️

View solution in original post

New Here?
Join us and watch the welcome video:
Announcements