Rewrite profile - any better way?
Hi,
I wonder is there is any simpler way to achieve something described below:
Scenario:
- Single VS - IP mapped to few external FQDNs
- Each external FQDN maps to virtual host on the same backend server (so traffic accepted only if there is Host header match in request send from BIG-IP to backend)
- There is possibility that some links returned from backend (in content) are not relative and can use backend srv FQDN.
Setup:
Local Traffic Policy forwarding traffic to appropriate pool based on host header in request from client - sure it could be one pool but because FQDN nodes has to be used I guess separate pools are needed - or not?
Then Rewrite profile with URI rules for each ext FQDN to int FQDN with Rewrite Header, Rewrite content set, like * -> * -> * -> * and so on
When redirect from http to https (send from backend) is needed then another Rewrite profile is necessary for HTTPS VS: * -> * -> * -> * and so on
It is working OK but requires plenty of objects to be configured, everything has to be entered by hand, in few places and cause a lot of work and possibility to make mistake :-(
Is there any other way (simpler, less error prone) to achieve the same goal?
Piotr