# Page Not Found

The URL `how-to/protect-an-existing-production-site-with-cloudguard-wafs-appsec-gateway` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Protect an existing production site with CloudGuard WAF's Gateway](https://waf-doc.inext.checkpoint.com/how-to/protect-an-existing-production-site-with-cloudguard-wafs-gateway.md)
- [Restrict Access to Backend Servers from CloudGuard WAF as a Service IPs Only](https://waf-doc.inext.checkpoint.com/how-to/restrict-access-to-backend-servers-from-cloudguard-waf-as-a-service-ips-only.md)
- [Integrate CloudGuard WAF with Prometheus](https://waf-doc.inext.checkpoint.com/how-to/integrate-cloudguard-waf-with-prometheus.md)
- [Use Terraform to Manage CloudGuard WAF](https://waf-doc.inext.checkpoint.com/how-to/use-terraform-to-manage-cloudguard-waf.md)
- [Configure Load Balancing when Using Cloud Guard WAF as a Reverse Proxy](https://waf-doc.inext.checkpoint.com/how-to/configure-load-balancing-when-using-cloud-guard-waf-as-a-reverse-proxy.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://waf-doc.inext.checkpoint.com/how-to/protect-an-existing-production-site-with-cloudguard-wafs-gateway.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.

### Option 2 — Browse the documentation index

Full index: https://waf-doc.inext.checkpoint.com/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://waf-doc.inext.checkpoint.com/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/how-to/protect-an-existing-production-site-with-cloudguard-wafs-gateway.md`).

You may also use `Accept: text/markdown` header for content negotiation.