Forum Discussion
hooleylist
Mar 11, 2011Cirrostratus
I always cringed when I see HTTP::disable as it disables the HTTP filter for the rest of the TCP connection. So even if you can't put the current request/response through the HTTP proxy for some reason, you don't get any further HTTP events (or HTTP load balancing, persistence, etc) for the life of the connection. I wish there was a simple way to detect the end of the next HTTP response and automatically re-enable the HTTP filter.
Aaron