administrator/frigate
1
0
Fork 0
mirror of https://github.com/blakeblackshear/frigate.git synced 2026-02-13 22:55:26 +03:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Update docs/docs/guides/reverse_proxy.md

Browse Source 
Co-authored-by: Nicolas Mowen <nickmowen213@gmail.com>
This commit is contained in:
Emil Sandnabba 2024-08-14 23:18:52 +02:00 committed by GitHub
parent 273e06ede4
commit d79bafc5b7
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/docs/guides/reverse_proxy.md
View File

@ -12,7 +12,7 @@ Before setting up a reverse proxy, check if any of the built-in functionality in
|-|-| |-|-|
|TLS|Please see the `tls` [configuration option](../configuration/tls.md)| |TLS|Please see the `tls` [configuration option](../configuration/tls.md)|
|Authentication|Please see the [authentication](../configuration/authentication.md) documentation| |Authentication|Please see the [authentication](../configuration/authentication.md) documentation|
|IPv6|[Advanced configuration #enabling-ipv6](../configuration/advanced.md#enabling-ipv6) |IPv6|[Enabling IPv6](../configuration/advanced.md#enabling-ipv6)
**Note about TLS** **Note about TLS**
When using a reverse proxy, the TLS session is usually terminated at the proxy, sending the internal request over plain HTTP. If this is the desired behavior, TLS must first be disabled in Frigate, or you will encounter an HTTP 400 error: "The plain HTTP request was sent to HTTPS port." When using a reverse proxy, the TLS session is usually terminated at the proxy, sending the internal request over plain HTTP. If this is the desired behavior, TLS must first be disabled in Frigate, or you will encounter an HTTP 400 error: "The plain HTTP request was sent to HTTPS port."