Forum Discussion
Vivek_Datta_263
Nimbostratus
NimbostratusiRule not getting executed for a URI apparently due to it's 6000+ char length
Hi all,
We have an iRule which directs a request to certain Pools depending on a regex match. However, we are observing that one particular URI doesn't follow this iRule and goes to random Pools...
Stanislas_Piro2
Cumulonimbus
CumulonimbusHi Vivek,
We have confirmed that the regex works fine, it's just that this particular request never hits the Pool selection iRule somehow, hence it keeps landing on random F5 pools
is it random pool or pool selected by previous request in the same TCP connection.
if a request doesn't match condition to assign pool, it will keep previous request assigned pool.
in you irule, can you check if URI length is right with command:
log local0. [string length [HTTP::uri]]
Do you really require regex to match URI instead of starts_with / contains / ends_with commands? Regex must be used only if necessary.
Can you filter on [HTTP::path], [HTTP::query] or on a dedicated query parameter [URI::query [HTTP::uri] myparam]?
