This fixed issue brought up recently. Here's a snippet from STATUS:
* We get an assertion failure when there is a regexp defined that
doesn't match in the response. Instead of relying on assertions,
we need to detect this case, print a fatal error message, and
quit.
...and here's how this looks in realtime:
bash-2.05 $ ./flood examples/round-robin-dynamic.xml
Regular expression match failed (<a href="([^"]*)">)
postprocessing failed (http://www.apachelabs.org/cgi-bin/htsearch).
Error running farmer 'Joe': Error string not specified yet.
bash-2.05 $
BTW. We use APR_EGENERAL a lot. It gets translated to this 'Error string
not specified yet', which sometimes leaves me clueless. Looks like we
need to have a bunch of defines with our own error codes.
Another thing on my personal TODO list is that we need to have some sort
of ID per url. It might just be a counter, or dedicated id like this:
<url id="placeorder" ... > so that if urllist is a bit bloated and
something bails out (regexp for example) you can quickly find bad url in
your config.
RBC as usual.
regards,
--
Jacek Prucia
7bulls.com S.A.
http://www.7bulls.com/
--- flood_round_robin.c.orig 2002-09-04 14:10:57.000000000 +0200
+++ flood_round_robin.c 2002-09-04 14:20:10.000000000 +0200
@@ -864,7 +864,10 @@
regcomp(&re, expanded, REG_EXTENDED);
status = regexec(&re, resp->rbuf, 10, match, 0);
- assert(status == REG_OK);
+ if (status != REG_OK) {
+ apr_file_printf(local_stderr, "Regular expression match failed
(%s)\n", rp->url[rp->current_url].responsetemplate);
+ return APR_EGENERAL;
+ }
size = match[1].rm_eo - match[1].rm_so + 1;
newValue = apr_palloc(rp->pool, size);
