Redirect to pool based on incoming HTTPS URI

Aaron - I've often encountered applications that won't function with an attached HTTP profile. I've just assumed it's because an HTTP profile causes the Virtual Server to require an HTTP request before opening a TCP connection to the pool member. While the HTTP profile is a requirement for L7 visibility, doesn't it also force the application to comply with certain standards? If it's SSL traffic not being decrypted on LTM, would these requests essentially look incorrect and therefore be kept from pool members?