Problem

-- A 'Connect to URL' filter which receives a response, but does not process it, may lead to an "Invalid Response" exception.

Resolution

* When a 'Connect to URL' filter receives a response which does not get processed, that data gets left behind on the connection and may be seen by policies that reuse the connection, leading to mysterious "Invalid Response" errors.  The fix is to consume the message, for example, with an HTTP Parser, or to simply avoid sending messages you will not use.