https to specific pool member port

Jason, sure there's a way. But, it boils down the your ability to determine how to route the traffic. Based on your description, I'll assume your config is setup like this

VIP (clientssl profile)
  +- POOL 
    +- MEMBER 10.10.10.10:*

Where you have a VIP setup with a clientssl profile to decrypt the traffic and a default pool setup with a single pool member configured with a wildcard port. Assuming that you can determine what the application is from something like the URL, you could do this

when HTTP_REQUEST {
  switch -glob [HTTP::uri] {
    "/app1/*" {
      node 10.10.10.10 80
    }
    "/app2/*" {
      node 10.10.10.10 81
    }
    "/app3/*" {
      node 10.10.10.10 82
    }
    "/app4/*" {
      node 10.10.10.10 83
    }
    "/app5/*" {
      node 10.10.10.10 84
    }
    "/app6/*" {
      node 10.10.10.10 85
    }
  }
}

That way when requests come in for URI's starting with /app1/, it will direct traffic to pool member 10.10.10.10 on port 80, /app2/ to port 81, etc.

You could alternately create 6 pools with a single member configured for a specified port. That way you define your pool in such a way that the health monitors can monitor the specific applications on the various ports independently. If you go that route, you would just use the "pool" command to assign traffic to a given pool based on the application.

Is this kind of what you were looking for? If not, send more details and we'll see what we can do.

-Joe