The checker now fails if the response body does not contain a match for the given regular expression. This uses the default std::regex grammar ("modified ECMAScript"), with default options (so case sensitive).
If minBytes and regex are both given, minBytes is checked first. It is allowed, but probably not that useful, to combine regex and method="HEAD" for the same checker.
Issue #20 is related, but this does not add anything related to reading local files. It could, if the libcurl configuration was changed to allow the FILE 'protocol'...
The checker now fails if the response body does not contain a match for the given regular expression. This uses the default std::regex grammar ("modified ECMAScript"), with default options (so case sensitive).
If
minBytes
andregex
are both given,minBytes
is checked first. It is allowed, but probably not that useful, to combineregex
andmethod="HEAD"
for the same checker.Issue #20 is related, but this does not add anything related to reading local files. It could, if the libcurl configuration was changed to allow the FILE 'protocol'...
...but at that point, the name
https
for this checker would be a bit confusing.