ProxySG Content Policy Language Guide
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:
1start transaction
2CPL Evaluation Trace:
3<Proxy>
4MATCH: trace.rules(all) trace.request(yes)
5<Proxy> action.set_header_1(yes)
6 | MATCH: | [Rule] action.set_header_2(yes) |
7 | 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:
12 GET http://www.my_site.com/home.html
13
14user: unauthenticated
15Discarded Actions:
16set_header_1
17set_header_2
18set header=set_header_3 (request)
19value='three'
20end 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.
280
