iRule ACCESS_ACL_ALLOWED VS APM Per-request Policy to insert APM variables in HTTP headers
Hi, When I need to insert APM session variable in a HTTP header, I use irule like the following : when CLIENT_ACCEPTED { set APMusername "" } when ACCESS_ACL_ALLOWED { if {$APMusername equals ""} { set APMusername [ACCESS::session data get session.logon.last.username] } HTTP::header insert "USER" $APMusername } But during Agility 2017 labs, we configured header insertion in Per-request policy which seems to be more integrated. F5 communicates on performance improvement using LTM Policies instead of iRules. is there such improvement using Per-request policy? Is Per-request policy not using more memory than a simple iRule?
big-ip web ui improvement
Hi! The BIG-IP provides a good option to configure device by using web interface. But sometimes classic dropdown menus starts bothering me, because you should always be aware to move your cursor straight between upper and lower menus while pointing to the submenu on the right, in case you missed it you are on the other menu already. It would be very nice if F5 could improve dropdown menus with the mechanism described in the article on the link below. http://bjk5.com/post/44698559168/breaking-down-amazons-mega-dropdown What do you think about it? Whether this measure will increase the level of user satisfaction?