# Page Not Found

The URL `c3650cdf-216a-4ba2-80b0-9d6c540b105e58d2670b-ea0f-484e-b88c-0e2c1499ec9bd71e4b42-8570-44e3-89b6-845326fa43b6` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Configure a new path/section of a site](https://waap.docs.link11.com/using-the-product/how-do-i.../configure-a-new-path-section-of-a-site.md)
- [Load balance traffic across my origin servers](https://waap.docs.link11.com/using-the-product/how-do-i.../load-balance-traffic-across-my-origin-servers.md)
- [Generate or renew my own SSL certificates](https://waap.docs.link11.com/using-the-product/how-do-i.../generate-or-renew-my-own-ssl-certificates.md)
- [Stream event data to a SIEM solution or other destination](https://waap.docs.link11.com/using-the-product/how-do-i.../stream-event-data-to-a-siem-solution-or-other-destination.md)
- [Authenticate mobile app users](https://waap.docs.link11.com/using-the-product/how-do-i.../authenticate-mobile-app-users.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://waap.docs.link11.com/using-the-product/how-do-i.../configure-a-new-path-section-of-a-site.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://waap.docs.link11.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://waap.docs.link11.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., `/using-the-product/how-do-i.../configure-a-new-path-section-of-a-site.md`).

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