datagroup value set to SSL?

thanks again Kevin. the application is a flex and is compiled at install time to only work with SSL in mind. so, even if i hit http:// locally on the server, it does the same thing (flash settings on right click of an otherwise blue background blank page). it's some sort of security i imagine (to not show the login if SSL handshake isn't there). tried insecure_compatible serverssl profile with http profile set to none, and the node on port 443 in the pool, but it just shows "page cannot be displayed".

The only way i got it to work so far through the F5 is using complete passthrough (no client/serverssl or http profiles, and node on 443), but i need an irule to steer traffic, so i'm stuck tryin to figure it out i guess. :-) i'm trying to imagine what is happening is the F5 is using a different set of ciphers when talking to the apache coyote server and there is a handshake failure resulting in the flex app sending the traffic to http, and giving that 500 error. that's odd though, because debug mode didn't show any handshake failures.

Speaking with Gary on F5 case 1-1307326921 just before the start of the 4th break, we took a trace using this command: tcpdump -ni 0.0:nnn -s0 -e host 10.33.225.20 and port 443 -w sslcap.pcap

And he also said he sees handshake failures in the trace. So, maybe they are a different breed of handshake failures that are eluding debug mode? i'll keep digging :-)