What is the logon.inc page in a per request policy good for (APM) ?
I was trying to do some customization of the per request page and noticed that nothing happened. Since I was not sure I did delete the complete content of that page leaving it empty. Result: no impact. If I want something changed in the per request page, I have to do it on the session policy page. Is that expected behaviour ? If yes... I was wondering... what is the usage of the logon.inc in a per request policy ?
Copy a branch of Per-request Policy
hi all! is there a way to copy a branch in a per request policy then paste it to another branch? i think that this can be done if the branch is already configured as a macro but in our scenario, all branches are configured manually. is there a way to do this or the only way is to configure it manually? Thank you.
APM - change CONNECT to GET to trigger per request policy
Hi, I wonder if this is at all possible to trick APM when CONNECT type of request is received to trigger Per Request Policy (PRP). According to my test on v13.0.0HF2 no matter what I will do when VS with Access Policy and PRP policy is receiving CONNECT request PRP is not triggered at all - probably by design, but maybe it's a bug? I would like to be able to use PRP objects to perform URL Filtering (based on target host FQDN) for CONNECT requests. I think - but it's just theory - that if I would be able to use iRule to change CONNECT HTTP/1.1 to GET http://www.host.com HTTP/1.1 then PRP would launch and do URL filtering stuff. Unfortunately my skills in iRule programing is rather limited so I will appreciate any help here. I suspect that maybe there is a way to use when CLIENT_CONNECTED and when CLIENT_DATA to detect CONNECT request, store is in table, change to GET and trick AMP to process it via PRP. Would it be possible? It's as well heavily related to be able to pass CONNECT request to another proxy after validating if host reported in CONNECT is allowed by PRP. Piotr