Posted By hoolio on 02/04/2008 2:45 AM
Hello,
What are the symptoms of the failure? To troubleshoot non-cookie persistence issues, you can check the persistence records via the GUI under Overview >> Statistics >> Persistence Records or via the CLI (using: watch -n1 'b persist all show all').
You might want to check to see if there is a value for the Authorization header before using the value of the header for persistence:
when HTTP_REQUEST {
if {[string length [HTTP::header value "Authorization"]]}{
persist uie [HTTP::header value "Authorization"]
log local0. "[IP::client_addr] -> [HTTP::host][HTTP::uri] had Authorization header value: \
[HTTP::header value "Authorization"]"
}
}
Aaron
Hi, I have just found this post today and I am running into an issue on v10.0.1 which is related to this.
The problem I have is that we have a v4 box which persists an application using the expression method and works fine:
http_header("Authorization")
Now that we have the new v10.0.1 boxes I have tried your rule above and persistence is simply not working.
Running a trace I see that some of the client requests don't have the Authorization header and this would explain why it's not working on v10.0.1, but this works on v4 as it is.
Is it possible that v4 used to check outside of the header, ie the body of the message?
If so how could this be done and used in a uie persistence iRule?
Thanks for any help.