Forum Discussion
LTM Policy Options Clarification
- Oct 23, 2023
1. Skip this condition if it is missing from the request:
Since conditions in the context of a rule are a "Match all", when a condition is not satisfied because it's actually not present in the request, as opposite from present but not matching, you may want to have different behavior and only match it the condition is present but its value is not matching.
2. Apply to traffic on remote/local side of external/internal interface:
Some conditions are contextual, for example you want to check for an IP address, so you need to specify which IP address, here's the matrix for the IP address example :
Client IP Remote, external F5 clientside (VS IP) Local, external F5 serverside (Self IP) Local, internal Server IP Remote, internal
1. Skip this condition if it is missing from the request:
Since conditions in the context of a rule are a "Match all", when a condition is not satisfied because it's actually not present in the request, as opposite from present but not matching, you may want to have different behavior and only match it the condition is present but its value is not matching.
2. Apply to traffic on remote/local side of external/internal interface:
Some conditions are contextual, for example you want to check for an IP address, so you need to specify which IP address, here's the matrix for the IP address example :
Client IP | Remote, external |
F5 clientside (VS IP) | Local, external |
F5 serverside (Self IP) | Local, internal |
Server IP | Remote, internal |
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com