Insert text to HTTP header via iRule event during APM execution

May be worth to try something like below. Let us know how the testing goes

when ACCESS_POLICY_AGENT_EVENT {
    if { [ACCESS::policy agent_id] eq "event_1" } {
        ACCESS::session data set session.custom.header "value"
        set header [ACCESS::session data get "session.custom.header"]
    }
 }
 when ACCESS_POLICY_COMPLETED {
    if {[info exists header]}{
	HTTP::header replace "headername" $header
	} else {
	 return
	}
 }
 

Hi SanjayP,

Thank you for your reply.

I tried to set the same under a single iRule as well as 2 separate iRules with ( when function each) to be executed one after another, but no luck.

The session.custom.header is getting set in first when block, but after the execution completion of APM, the header replace\insertion is still not working.

Can you enable some logging and see what's happeing. also edit the iRule to add "insert header"

when ACCESS_POLICY_AGENT_EVENT {
    if { [ACCESS::policy agent_id] eq "event_1" } {
        ACCESS::session data set session.custom.header "value"
        set header [ACCESS::session data get "session.custom.header"]
		log local0. "header: $header"
    }
 }
 when ACCESS_POLICY_COMPLETED {
    if {[info exists header]}{
	log local0. "header found"
	HTTP::header insert "headername" $header
	log local0. "header inserted with value $header"
	} else {
	log local0. "no header added as event doesn't match"
	 return
	}
 }

"

I think that to set headers or cookies with the event "ACCESS_POLICY_COMPLETED", you need to use the "ACCESS::respond", as I gave in the example in my previous update as "ACCESS_POLICY_COMPLETED" by default does not overide the default APM response after the policy check is completed:

Example:

https://devcentral.f5.com/s/question/0D71T000006gzth/detail?s1oid=00D00000000hXqv&s1nid=0DB1T0000008Ony&emkind=chatterCommentNotification&s1uid=0051T000008eyBa&emtm=1617222886798&fromEmail=1&s1ext=0

https://clouddocs.f5.com/api/irules/ACCESS_POLICY_COMPLETED.html

The "ACCESS_ACL_ALLOWED" can be tested as it seems much easy and you can just add a header. So maybe just replace "ACCESS_POLICY_COMPLETED" with "ACCESS_ACL_ALLOWED" on the conbined iRule and if there are issues try "ACCESS::respond" with the event "ACCESS_POLICY_COMPLETED" and enable logs with ''log local0'' to see where is the issues.

https://clouddocs.f5.com/api/irules/ACCESS_ACL_ALLOWED.html

Hi Nikoolayy1,

"ACCESS_POLICY_COMPLETED" with "ACCESS_ACL_ALLOWED" on the conbined iRule didn't helped much. But yes enabling log local0 helped to trace the flow. Thanks much for your help. Cheers.