Nesting a redirect to another pool?

grrr...

Matt - yours isn't quite doing it.

http://www.foo.com/bar resolves to https://www.foo.com/

thought maybe it was the HTTPS, but

https://www.foo.com/bar resolves to itself, with 404 NOT FOUND

I thought maybe it was that nothing existed at http://backend_pool2/bar, maybe I needed to put something there, so I created a site there, but that didn't change anything

Is it feasible to point a [HTTP::host][HTTP::uri] to a Pool? or do I need to create a Virtual Server for [HTTP::host][HTTP::uri] to point to?

Once again, here's what I'm trying to do:

[HTTP::host] resolves to https://www.foo.com using a standard iRule to redirect HTTP to HTTPS, and content is served by Virtual Server nodes in Pool1

[HTTP::host][HTTP::uri] when uri = "/bar" should resolve to content served by nodes in Pool2

the iRules I have running (in order) are:

iRule 1

when HTTP_REQUEST {     
 if {[HTTP::uri] equals "/bar"} {     
 HTTP::uri [string map {"bar" ""} [HTTP::uri]]    
 pool bar_pool    
 }     
 }

iRule2

when HTTP_REQUEST {   
 HTTP::redirect https://[HTTP::host][HTTP::uri]   
 }