For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

John_LeMay_1062's avatar
John_LeMay_1062
Icon for Nimbostratus rankNimbostratus
Sep 27, 2006

Combining http_request and client_accepted?

I'm working on putting together what I think will be a relatively complex rule - at least it will be for me. So far my irule experience been limited to uri rewrites and redirects. However, I now have ...
application delivery
dev
devops
iRules
John_LeMay_1062's avatar
John_LeMay_1062
Icon for Nimbostratus rankNimbostratus
Sep 27, 2006
Wow, that greatly simplifies this process. I'm getting away from the original subject here, but I have one last piece of this and I believe I'll have a working site.

 

 

As I mentioned previously, the http servers in this case are listening on an odd port - 81 to be exact. We want the clients to connect via https. What I have done so far is configured a VS that listens on 443, has a client SSL profile, and has the irule and a pool as resources. The pool has two members, both listening on port 81.

 

 

What I expected was the client would always talk to the BigIP via https and all of the port 81 "stuff" would be handled behind the scenes. What is happening now is the client is being redirected to http://server/path/path:81. I'm not completely certain yet if this maybe a behavior of the application instead of a BigIP issue.

 

 

Should there be a simple way to accomplish what I'm describing, or am I going to be stuck running multiple virtual servers and not being able to run the client side over https?