Does LTM support websocket protocol with cookie persistence?

What if you add LB::select before HTTP::disable to force a pool decision?

I tried it in my lab and it chose the right pool member all the time, but my stats was a bit strange. Worth a try at least?

when CLIENT_ACCEPTED { 
    HTTP::enable
} 

when HTTP_REQUEST { 
    if { ([string tolower [HTTP::header value Upgrade]] equals "websocket" ) && ([string tolower [HTTP::header value Connection]] equals "upgrade" ) } { 
        log local0. "HTTP Disable" 
        LB::select
        HTTP::disable
    }
}

/Patrik