Our company has just changed up the front end of one of its web products, and it's broken my Geo-redirection
Previously, users hit https://www.product.com - and were redirected to either https://au.product.com or https://uk.product.com depending on their originating IP - and were presented with a login link for the product concerned.
This worked fine, and has done so for months.
However, a recent change demanded by marketing has led to the following situation
User hits http://www.product.com (yes, no https - yet. This will change when I get a spare minute)
User clicks "Login" link and gets a login window presented in an i-Frame - which needs to be geo-redirected to either https://au.product.com or https://uk.product.com
This isn't working - I've figured out it's most likely because the content from the i-Frame is hitting the F5 differently somehow, and not being caught by the iRule doing the redirection - but I don't know how to fix it.
Can anyone shed some light on how I might get this to work? Or at least tell me it's not possible, so I can tell the developers to go re-think their design to get rid fo the i-Frame?
For relevance - BigIP 1600, running LTM only, version 11.5.3 HF2
Thanks for any pointers.
Thanks for the input - I found the answer, and it boiled down to the way I had the geo-redirect iRule written.
Chalk this up to administrator is an idiot error.
I haven't worked with iFrame but it looks to be some kind of HTML. I am assuming it requires HTTP and hence, it should work with F5's iRule. Were you able to utilize the developers tools in chrome or any similar tool to check the headers ? May be even a packet capture might help.
First off, iframes aren't great. There are much better options these days (JS/CSS based like Angular, jQuery).
Having said that, what is URL the iframe specifies?