# Filter by Content

There are several ways to filter requests based on their content.

## Recommended Method: Session Profiling

1. Create one or more lists of content filters in [Session Profiling](/v2.14/product-walkthrough/security/session-profiling.md), with appropriate tags. 
2. Create [ACL Policies](/v2.14/product-walkthrough/security/profiles/acl-policies.md) for each tag with appropriate actions (Bypass, Deny, or Allow).
3. Include the ACL Policies in one or more [ACL Profiles](/v2.14/product-walkthrough/security/profiles.md).
4. Include the ACL Profiles in one or more [Security Profiles](/v2.14/product-walkthrough/settings/web-proxy.md#security-profiles).

## Other Methods

[Custom Signatures](/v2.14/product-walkthrough/security/profiles/acl-policies.md#custom-signature) can be used for specifying content restrictions. They are included within [ACL Policies](/v2.14/product-walkthrough/security/profiles/acl-policies.md), which are used within [Profiles](/v2.14/product-walkthrough/security/profiles.md), which are assigned to various locations of your site/application on the [Web Proxy](/v2.14/product-walkthrough/settings/web-proxy.md) page.

[Args Analysis](/v2.14/product-walkthrough/security/args-analysis.md) examines the characters found in arguments. Depending on its mode, it can block requests if unexpected characters are found, or pass them on to the WAF for further inspection. It can also act as an inverse content filter; those requests with arguments which contain only whitelisted characters can bypass WAF filtering. 

{% hint style="warning" %}
Custom Signatures and Args Analysis will be deprecated in a future release. For content filtering, it is recommended that you use the first method based on Session Profiling instead.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://waap.docs.link11.com/v2.14/using-the-product/how-do-i.../filter-by-content.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.