Skip to content

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

Open
awesome-doge wants to merge 1 commit into
ton-blockchain:mainfrom
awesome-doge:ton-proxy-public-gateway
Open

awesome-doge wants to merge 1 commit into
ton-blockchain:mainfrom
awesome-doge:ton-proxy-public-gateway

Conversation

@awesome-doge

Copy link
Copy Markdown

The TON Proxy page explains how to open TON Sites by running rldp-http-proxy locally and setting it as the browser's HTTP proxy. A reader who only wants to look at a .ton site has no lighter option on the page. Earlier versions of the docs mentioned a public gateway for that; the restructured pages no longer do.

This adds a short "Without installing anything" subsection under "Forward proxy (client-side)":

  • one sentence on public HTTPS gateways;
  • one example, <name>.ton → https://<name>.ton.website;
  • a privacy note that a gateway sees the requests it forwards, so sensitive use should run a local proxy.

Disclosure: I run ton.website. Happy to reword it as a neutral list or add other public gateways if you know of any.

Checked locally: cspell and prettier --check pass on the changed file.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant