Valid events in STREAM_MATCHED event? (avoiding

Hi,

 

 

I was thinking that you could make decisions based on request or response data without actually collecting the HTTP data by using the stream profile. For example, this person (Click here) was trying to re-select a new node if a specific string was found in the response content. If you could use a stream command to look for that string and then put the reselect code in the STREAM_MATCHED event, you could avoid collecting the response data.

 

 

This is what I was thinking:

 

 

when HTTP_RESPONSE {
    Look for the error text in the response content
   STREAM::enable
   STREAM::expression @some error text@@
}
when STREAM_MATCHED {
    Found the error string, so select a new node"
   LB::mode rr
   LB::detach
   HTTP::retry $request
}

 

Error: command is not valid in current event context (STREAM_MATCHED)] [HTTP::retry $request]

 

 

 

However, in 9.2.4, I get an error stating the HTTP::retry command isn't valid in the current event. When I work around that error using eval, and the HTTP::retry command is triggered, I see a TCL error: "Not connected". I assume this means the proxy isn't in a state where it can resend an HTTP request.

 

 

Is this expected? If so, are there any workarounds you can think of to use a stream profile to inspect request or response data without collecting it?

 

 

Aaron