ProxySG Content Policy Language Guide
230
delete_matching( ) Deletes all components of the specified header that contain a substring matching a regular-expression
pattern.
Note: An error results if two header modification actions modify the same header. The error is noted
at compile time if the conflicting actions are within the same action definition block. A
runtime error is recorded in the event log if the conflicting actions are defined in different
blocks.
Syntax
delete_matching(header, regex_pattern)
where:
•header—A header specified using the following form. For a list of recognized headers, see
Appendix C.
❐request.header.header_name— Identifies a recognized HTTP request header.
❐response.header.header_name—Identifies a recognized HTTP response header.
❐request.x_header.header_name—Identifies any request header, including custom headers.
❐response.x_header.header_name—Identifies any response header, including custom
headers.
•regex_pattern—A quoted regular-expression pattern. For more information, refer to Appendix
E, “Using Regular Expressions,” in the Blue Coat ProxySG Configuration and Management Guide.
Layer and Transaction Notes
Do not use in <Exception>, <Forward>, or <Admin> layers.
See Also
•Actions: append( ), delete( ), rewrite(header, regex_pattern,
replacement_component), set(header, string)
•Conditions: request.header.header_name=, request.header.header_name.address=,
request.x_header.header_name=, request.x_header.header_name.address=,
response.header.header_name=, response.x_header.header_name=