Forum Discussion
Tom_Thunem_9204
Nimbostratus
Jul 13, 2006add flag to http header based on which pool is selected
we have a rule in place that selects a pool based on the source IP. in 4.x has anyone ever added a "flag" to the http header to indicate which pool the traffic was sent to?
John_LeMay_1062
Nimbostratus
Sep 27, 2006Wow, 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?