Snat pool choice based on destination URL

Thanks to everyone for their help. It turns out that some of the outbound requests are using SSL, so inspection of the URI has become difficult at best, we aren't using SSL encrypt/decrypt on the BigIPs. So at this point we have multiple virtuals using our private IP space as the destination, and using the partners IPs as the members of a pool for that virtual.

I believe though, that I should be able to modify your above example a bit and get some more flexibility, not having to manually insert the member IPs into the pool, which is effectively bypassing our partners DNS magic.

I was thinking of something like this.

rule partner_snat_rule {
  when CLIENT_CONNECTED {
      use snatpool snat_a
      use node a.partner.com 443
  }
}

Though when I try it, it says that "use node" requires an IP. I thought that HTTP::host was a hostname, not an IP, so the above example wouldn't work?

Thanks,

Ethan