Forum Discussion
Lucas_Thompson_
Historic F5 Account
Clientless-mode (if it's inserted) will cause the 302 to /my.policy to NOT occur. So if you're seeing that, then your header insert isn't working for some reason. The lack of a host header in the client request may be interfering also.
Try using this command on the connection along with your header insert, and add a log statement to make sure it's executing:
https://devcentral.f5.com/wiki/iRules.ACCESS__restrict_irule_events.ashx
Bala_128530
Oct 29, 2015Nimbostratus
Hi,
Thanks for your update, I have tried this option. It’s keep on looping the login.
1) HTTP::redirect "/"
Client 1xx.1yy.1.30:52290 -> mysite.com/DWeb/Settings/CommonImages/Branding.xml (request)
Client 1xx.1yy.1.30:52291 -> mysite.com/my.policy (request)
Client 1xx.1yy.1.30:52292 -> mysite.com/my.logout.php3?errorcode=19 (request)
site redirected
Client 1xx.1yy.1.30:52292 -> mysite.com/ (request)
Client 1xx.1yy.1.30:52293 -> mysite.com/my.policy (request)
Client 1xx.1yy.1.30:52294 -> mysite.com/my.logout.php3?errorcode=19 (request)
site redirected << looping>>
2) I have tried specific URL, still the same result.
HTTP::redirect "https://mysite.com/DWeb/Settings/CommonImages/Branding.xml
mysite.com/DWeb/Settings/CommonImages/Branding.xml (request)
mysite.com/my.policy (request)
mysite.com/my.logout.php3?errorcode=19 (request)
: site redirected
mysite.com/DWeb/Settings/CommonImages/Branding.xml (request) <= looping
Each redirection APM creates new session. Each session ends with “User-Agent header is absent or empty”
Is there any other variable to validate user session to allow.