> For the complete documentation index, see [llms.txt](https://docs.elimity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elimity.com/reference-manual/v3.46.6/installation/http-s-proxy.md).

# HTTP(S) proxy

We strongly recommend including a production-grade HTTP(S) proxy in each deployment of Elimity Insights. For our SaaS customers we include this by default.

Most cloud providers offer an HTTP(S) proxy (e.g. Google Cloud Load Balancing, Azure Load Balancer) that integrates well with their CaaS / VMaaS products. If using your cloud provider's proxy is not an option, then installing one manually on e.g. Windows Server is also possible. We suggest to take a look at [Caddy](https://caddyserver.com/), a widely-used open-source HTTPS server with excellent proxying capabilities. The remainder of this page contains some additional guidelines for setting up Caddy as an HTTP(S) proxy for Elimity Insights on Windows Server.

## Installing Caddy on Windows Server

To install Caddy as an HTTP(S) proxy for Elimity Insights on Windows Server we recommend to just deploy [their official Docker image](https://hub.docker.com/_/caddy). Refer to the snippet below as a starting point for your `docker-compose.yml` file:

```yaml
services:
  caddy:
    image: caddy
    ports:
      - 80:80
      - 443:443
    restart: always
    volumes:
      - .\caddy:C:\etc\caddy

  insights:
    image: europe-west1-docker.pkg.dev/elimity-general/docker/insights:v3.41.0-nanoserver-ltsc2022
    restart: always
    volumes:
      - .\insights:C:\app\config 
```

Of course you'll also need to configure Caddy. The official documentation includes [a great tutorial about writing `Caddyfile`s](https://caddyserver.com/docs/caddyfile-tutorial), here's a template you can build on (place it at `.\caddy\Caddyfile`):

```
elimity.example.com

reverse_proxy insights

tls cert.pem key.pem
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.elimity.com/reference-manual/v3.46.6/installation/http-s-proxy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.