pool based on https host header

Hi,

 

 

I drove into work this morning thinking that it was going to be a 5 minute job to set up and irule to inspect the http::host header on incoming http *and* https connections and assign a pool based upon that on a single vip. seems i'm actually wrong about the https side? as i understood it, https starts by doing a CONNECT [hostname] and then moves on to ssl handshaking once that's done. so i can see that initial itty bitty bit of plain text and off it goes to a pool to do the ssl stuff, which i'm not offloading. This doesnt' actually seem to be the case in the cold morning light. Am i confusing this with the behaviour here with that of https via a proxy? does the end server actually never see a "CONNECT"?

 

 

Cheers

 

 

Chris