From 348c833d5830358cba27e56cc4da44fc5b0156fb Mon Sep 17 00:00:00 2001 From: unspec Date: Thu, 12 Dec 2019 13:28:21 +0000 Subject: [PATCH] Update faq.md --- faq.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/faq.md b/faq.md index 32e582d..5bbc1a0 100644 --- a/faq.md +++ b/faq.md @@ -22,7 +22,7 @@ There are several reasons why a particular service / CDN / website might not be 1. It's not technically possible to cache it. Many popular websites, including video streaming sites and even some games CDN's use SSL Encryption (i.e https URLs) to serve their content. Because the client opens a secure connection directly to the host, there is no way for the network operator to see what they are downloading, nor cache it. Whilst there are several approaches to work around this, such as MITM techniques, they usually rely on control over the client device to control SSL Certificates - control somebody running a BYOC LAN typically does not have over the devices customers bring. - https://github.com/uklans/cache-domains/issues?q=is%3Aissue+is%3Aopen+label%3Ahttps-cantfix Contains a list of game CDNs that we would like to include, but cannot for this reason. + - https://github.com/uklans/cache-domains/issues?q=is%3Aissue+is%3Aopen+label%3Ahttps-cantfix Contains a list of game CDNs that we would like to include, but cannot for this reason. 2. It's out of scope for a LAN. We try to keep this list targeted towards people running LANs. Whilst some none game-related CDNs are included for things like windows updates that use internet bandwidth at LANs, we do not go searching for unrelated sites / hostnames. @@ -34,4 +34,4 @@ There are several reasons why a particular service / CDN / website might not be [lancachenet/sniproxy](https://github.com/lancachenet/sniproxy) is part of the lancache project and allows hostnames that serve BOTH http and https content to be included in this list. Traffic going to that hostname on port 80 (http) will hit lancache and be cached, whilst traffic on port 443 (HTTPS) is passed straight through to the internet. -It does not allow https / SSL content to be inspected or cached. Hostnames that serve all or almost all https traffic are still unlikely to be good candidates for this list, as it just places load on the cache box but does not save any internet bandwidth. \ No newline at end of file +It does not allow https / SSL content to be inspected or cached. Hostnames that serve all or almost all https traffic are still unlikely to be good candidates for this list, as it just places load on the cache box but does not save any internet bandwidth.