Forum Discussion
What_Lies_Bene1
Apr 22, 2013Cirrostratus
I think the persistence would be maintained for the actual HTTP traffic as long as it's flowing over different TCP connections. The issue is if the same connection within a session is used for the HTTP and non-HTTP traffic. Once the HTTP::disable command is used it will apply for the lifetime of that connection and HTTP::enable won't re-enable it as the CLIENT_ACCEPTED event is only fired once when a connection is first established. Move it to a HTTP event and that won't fire either as HTTP processing has been disabled. Catch 22 really.
However, you might be lucky and find a new connection is established just for the non-HTTP traffic - lets hope so.