Forum Discussion
som_86408
Nimbostratus
Nimbostratussource IP based persistence
Hi,
I have a requirement where clients must stick to the same server for HTTP to HTTPS and decided to use source address persistence but in a document (http://devcentral.f5.co...
hoolio
Cirrostratus
CirrostratusHello Andy,
You can enter the text of the rule you write in the GUI's rule page and it will verify the syntax before saving the rule.
Else, you can copy the /config/bigip.conf file to a temporary file, edit it to add your rule and then use 'b verify load /config/bigip_test.conf' to verify the syntax of the file.
When you're happy with the changes you can copy the temporary file over the existing bigip.conf file and run 'b load' to initialize the changes. Note that running 'b load' will reset all current connections through the BIG-IP so it should be used to test on a production unit.
Aaron
Tim_Sil_178134I am trying to implement a similar feature on our F5 but I don't understand how this is working. When my monitors detect that the pool members are all down the F5 just stops responding on the Virtual Server IP address so this rule never gets applied. Is there additional configuration necessary to make an iRule like this work within the virtual server or health monitor?
mrvIn my opinion indication of 404 status by redirection (302) to existing page (Error page -200) is against the rule that URL should indicate rosource.
In other words as long as resource doesnt exist, the error page should be dispalyed but also return 404 status.
Your solution works in following way:
Request -> 302 -> 200
302 means resource moved, not 'not found'
Is there a way to make forward (forward error page contents) instead of redirect?
![\"F5](\"https://www.f5.com/content/dam/f5/f5-logo.svg\"){kind=logo}
