> For the complete documentation index, see [llms.txt](https://docs.link11.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.link11.com/product-guides/secure-cdn/faq/link11-cdn-deployment-with-waap-products.md).

# Link11 CDN Deployment with WAAP Products

Link11 offers three different configurations for handling customer traffic over our CDN in combination with the WAAP Security Proxy.

{% hint style="info" %}
Note that the different configurations are related to your choice between [static and full page caching](/product-guides/secure-cdn/faq/static-vs-full-page-caching.md).
{% endhint %}

## Full Page Caching and WAAP Protection <a href="#link11cdndeploymentwithwaapproducts-fullpagecachingandwaapprotection" id="link11cdndeploymentwithwaapproducts-fullpagecachingandwaapprotection"></a>

<figure><img src="/files/eMOe5uVdA2Nt9d0hYTth" alt=""><figcaption></figcaption></figure>

When using full page caching and the Link11 WAAP service, all traffic is routed to the Link11 CDN nodes. Uncached content requests are then forwarded from the CDN nodes to the Link11 WAAP proxy instances. Clean traffic is forwarded to the customer origin.

| ➕ Pros                                                                    | ➖ Cons                                                                                                                              |
| ------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| Full caching of all content                                               | Because both the CDN and WAAP services bill based on the total traffic received, this option tends to lead to higher monthly costs. |
| Origin fully protected, with all requests analyzed before being forwarded | Potential to cache dynamic content if cache control headers are misconfigured.                                                      |
| Easy set up with just a single DNS change                                 |                                                                                                                                     |

**Customer use case**: For customers that have not configured their websites to access cached content from a separate URL, or for customers where security is the paramount concern.

| **Cost**        | Highest |
| --------------- | ------- |
| **Security**    | Highest |
| **Performance** | Lowest  |

## Static Caching and Full WAAP Protection <a href="#link11cdndeploymentwithwaapproducts-staticcachingandfullwaapprotection" id="link11cdndeploymentwithwaapproducts-staticcachingandfullwaapprotection"></a>

<figure><img src="/files/iNFQOc9LFVveKW0Qh0D3" alt=""><figcaption></figcaption></figure>

When using a separate subdomain for static content and also leveraging Link11 WAAP, caching can be enabled on just the subdomain. This allows most requests to be processed on the WAAP Proxy instance with only the calls for static content being redirected to the CDN nodes. Requests for expired cache content are then forwarded to the Link11 WAAP Proxy Instances for analysis. Clean traffic is then forwarded from the Link11 WAAP Proxy Instances to the Customer Origin.

| ➕ Pros                                                                                        | ➖ Cons                                                                                       |
| --------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| Bypassing CDN nodes for non static content improves initial request handling performance      | More complicated set up for customers as static content needs to be hosted on a separate URL |
| Better cost as only static content is counted in the billing for both CDN and WAAP Service(s) |                                                                                              |
| Origin fully protected                                                                        |                                                                                              |

**Customer use case**: For customers that have a separate URL for cached content (or are willing/able to modify their application to do this) and who want lower costs but still highly value security.

| **Cost**        | Medium  |
| --------------- | ------- |
| **Security**    | Highest |
| **Performance** | Medium  |

## Static Caching and Partial WAAP Protection <a href="#link11cdndeploymentwithwaapproducts-staticcachingandpartialwaapprotection" id="link11cdndeploymentwithwaapproducts-staticcachingandpartialwaapprotection"></a>

<figure><img src="/files/JrfBtHSwE9ku0EP8GJ7N" alt=""><figcaption></figcaption></figure>

When using a separate subdomain for static content and also leveraging Link11 WAAP Protection, cache content requests can bypass the Link11 WAAP Protection while all non cache requests are protected. Requests for expired cache content are forwarded from the CDN nodes directly to the customer origin while non cache content requests are analyzed by the Link11 WAAP Proxy Instances before Clean traffic is forwarded to the Customer Origin.

| ➕ Pros                                                                                | ➖ Cons                                                                                        |
| ------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| Bypass CDN Nodes for non static content improves initial request handling performance | More complicated set up for customers, as static content needs to be hosted on a separate URL |
| Best cost as no CDN content is counted towards the billing for WAAP Service(s)        | No WAAP analysis or protection on the requests from the CDN nodes                             |

**Customer use case**: For customers that have a separate URL for cached content (or are willing/able to modify their application to do this) and who prioritize cost or performance the highest.

| **Cost**        | Lowest  |
| --------------- | ------- |
| **Security**    | Lowest  |
| **Performance** | Highest |