Filter
Top Products
ProxySG Content Policy Language Guide
280
Policy: Action discarded, 'set_header_1' conflicts with an action already committed
The conflict is reflected in the following trace of a request for //www.my_site.com/home.html:
1 start transaction ------------------------------
2 CPL Evaluation Trace:
3 <Proxy>
4 MATCH: trace.rules(all) trace.request(yes)
5 <Proxy> action.set_header_1(yes)
6 [Rule] action.set_header_2(yes)
7 MATCH: action.set_header_1(yes)
8 MATCH: action.set_header_2(yes)
9 MATCH: action.set_header_3(yes)
10 connection: client_address=10.10.0.10 proxy_port=36895
11 time: 2003-09-12 15:56:39 UTC
12 GET http://www.my_site.com/home.html
13 User-Agent: Mozilla 8.6 (Non-compatible)
14 user: unauthenticated
15 Discarded Actions:
16 set_header_1
17 set_header_2
18 set header=set_header_3 (request)
19 value='three'
20 end transaction --------------------------------
Notes:
• Layer and section guard expressions are indicated in the trace (lines 7 and 8) before any rules
subject to the guard (line 9).
• Line 15 indicates that actions were discarded due to conflicts.
• Lines 16 and 17 show the discarded actions.
• Line 18 shows the remaining action, while line 19 shows the effect of the action on the header
value.