Forum Discussion
hooleylist
May 19, 2009Cirrostratus
As cmbhatt and Denny said, monitors would be a much better solution. You could configure a standard HTTP monitor which checks for a string that isn't found in the 200 response with an error message. Or you could check for a 200 with a normal monitor and then look for (?:JRun closed connection|Server Error) in a reverse monitor.
I'd try to avoid buffering any amount of response content for every response just to check for an error string. I don't think the added value of hiding an error message from some clients is worth the added overhead and latency for all clients.
Aaron