Feature Requests Allow testing for the Content-Length of the response

Closed

Allow testing for the value of header Content-Length, testing for a minimum response size, e.g. 10kb.

Use cases for this, mostly related to static websites:

  • when a server is under low available memory it may return a zero length content with an HTTP 200 response (happened to me today with Apache httpd with mpm-event configured)
  • when an app can't properly connect to the database it might not correctly return the expected content (e.g. render a page missing the main content, but with opening and closing html tags), and still generate an HTTP 200 response
  • when the build process of a static website can't properly fetch all the content, it might generate only partially rendered pages
Vinicius
Created on March 17, 2026 · Last update on March 18, 2026
1 Comment
Adrien Rey-Jarthon
Changed status to Closed

Thanks for this suggestion, but all the use cases described can already be covered decently with the string match feature. So I don't think it would be wise to complexify the code and UI with another option for this. It's possible I'll allow matching on HTTP headers in the future (using the same "contains" field), but in that case it's gonna be exact match (e.g. Content-Lenght: 823). So you are better of using the "contains" feature with a string that you know indicates a healthy site.

Like   Mar 18, 2026 13:22

Sign in to comment