Forum Discussion
You can change the HTTP Compression and Webacceleraration profile by using a LTM Local Traffic Policy. In regards to modifying the TCP profile, I think you're out of luck.
But what you can do is create a second Virtual Server which has the exact settings you want for your Indian-based customers (second public DNS needed). What you can then do is issue a HTTP redirect from the main Virtual Server/Service to that Indian-specific Virtual Server/Service based on customer's GeoLocation (using an iRule).
- The initial TCP handshake, SSL handshake and L7 HTTP request will still use the settings from your main Virtual Server, but any consequent requests can benefit from your optimized profiles.
- Over time, your Indian-based customers will refrain from using the main DNS as they are aware of the existence of your second DNS name dedicated for their region.
- Hannes_RappOct 18, 2016Nimbostratus
If you're aiming to just test the benefits of your optimized profiles first, create a second Virtual Server with the same target IP address, but take advantage of the Source IP Address field (closest-match source-IP VIP will get the connection). If you know from which IP address the test connections will be coming from, your test scenario will be very straight forward and there's no need to use any iRules.