Using a reverse proxy performs better than doing SSL encryption within Unity as part of the game server process:
* Unity is single-threaded, while the reverse proxy is a separate process that's generally engineered to enterprise class performance and is multi-threaded.
* Encryption is computationally expensive, so better to not bog down Unity with that workload.
* Unity / mono may not be up to date on TLS version or be able to read the latest certificates.
This section has instructions for both [Linux](/docs/manual/transports/websockets-transport/reverse-proxy/linux.md) and [Windows](/docs/manual/transports/websockets-transport/reverse-proxy/windows.md).
---
# 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://mirror-networking.gitbook.io/docs/manual/transports/websockets-transport/reverse-proxy.md?ask=
```
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.