mirror of
https://github.com/klzgrad/naiveproxy.git
synced 2025-04-19 17:11:01 +00:00
update README
This commit is contained in:
parent
a8fe4ebe81
commit
7d9e553903
1 changed files with 3 additions and 1 deletions
|
@ -53,6 +53,8 @@ route {
|
|||
```
|
||||
`:443` must appear first for this Caddyfile to work. For more advanced usage consider using JSON for Caddy 2's config.
|
||||
|
||||
See also: [Run Caddy as a daemon](https://github.com/klzgrad/naiveproxy/wiki/Run-Caddy-as-a-daemon)
|
||||
|
||||
Locally run `./naive` with the following `config.json` to get a SOCKS5 proxy at local port 1080.
|
||||
```json
|
||||
{
|
||||
|
@ -125,4 +127,4 @@ But if you don't need the best performance, and unobfuscated TLS-in-TLS somehow
|
|||
|
||||
### Why no "CDN support"?
|
||||
|
||||
Take Cloudflare for example. https://www.cloudflare.com/terms/ says: "Use of the Service for serving video (unless purchased separately as a Paid Service) or a disproportionate percentage of pictures, audio files, or other non-HTML content, is prohibited." Proxying traffic is definitely prohibited by the terms in this context.
|
||||
Take Cloudflare for example. https://www.cloudflare.com/terms/ says: "Use of the Service for serving video (unless purchased separately as a Paid Service) or a disproportionate percentage of pictures, audio files, or other non-HTML content, is prohibited." Proxying traffic is definitely prohibited by the terms in this context.
|
Loading…
Add table
Reference in a new issue