Redirect or Append URI with a new path /newpath, for a https website.

Do you have a client SSL profile applied to your 443 virtual server? You'll need to decrypt the SSL in order to inspect the HTTP traffic and redirect. The client SSL profile will terminate the SSL at the BIG-IP so you can perform layer 7 functions like HTTP redirection.

I do not have that. What's the best way to create one?

Try to obtain the certificate and private key from the server in question. Then load that into your LTM and apply it to a client SSL profile. Then apply that client SSL profile to your 443 virtual server.

You might also want to make sure you capture "" as the path.

HTTP_REQUEST 
    { if {[HTTP::path] eq "/" || [HTTP::path] eq ""} {
        HTTP::path "/newpath" }
        pool target_pool
    }

What if I need to use a vanity name? And need to redirect that to the '/path' ?

http://vanityname/ needs to point to https://exam.mycomp.com/newpath ?

What is the best way to incorporate that? Thanks.

when HTTP_REQUEST {

if {[HTTP::host] eq "vanityname" || [HTTP::host] eq "vanityname.mycomp.com" } {

HTTP::redirect "https://exam.mycomp.com/newpath/"

} }

So I confirmed this works on port80/http.

Unfortunately, I need to get this working on port443/https on the virtual server and the backend nodes in the pool.

I know I probably need a client ssl profile, but do I need a server ssl profile for the backend nodes listening on 443?

Does the client ssl profile use the same certificate as the server ssl profile? Should the certificate be for the vanityname or the actual name?

this is the current one. I've tested this on a test vip on 443. It appears to work.

when HTTP_REQUEST {

if {[HTTP::host] eq "vanityname" || [HTTP::host] eq "vanityname.mycomp.com" } {

HTTP::redirect "https://exam.mycomp.com/newpath/"

}

}