Skip to content

feat(proxy): mention public HTTPS gateways for opening TON Sites #2345

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
awesome-doge wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −0
Open

feat(proxy): mention public HTTPS gateways for opening TON Sites #2345

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions content/foundations/web3/ton-proxy.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,10 @@ Configure the browser to use `127.0.0.1:8080` as an HTTP proxy. TON Sites are th
| `-d` | `--daemonize` | Daemonize the process |
| `-l <file>` | `--logname` | Log file path |

### Without installing anything

Public HTTPS gateways run a forward proxy on a server and serve TON Sites at ordinary web addresses. For example, [ton.website](https://ton.website) opens `<name>.ton` at `https://<name>.ton.website`. A gateway sees every request it forwards; for anything sensitive, run a local forward proxy as described above.

## Reverse proxy mode

`rldp-http-proxy` also operates as a reverse proxy for servers hosting TON Sites. In this mode it accepts inbound ADNL connections and forwards HTTP requests to a local or remote web server. Two implementations are available.
Expand Down
Loading