Telegram Desktop is preparing a new WEB Proxy. A new proxy type is appearing in the client that uses WebView to transport regular MTProxy traffic through a web-based transport.

It works roughly like this: Telegram Desktop routes its MTProxy traffic through a WebView-based HTTPS/WebSocket transport as a multiplexed stream.

A separate transport with its own frame format — OPEN, DATA, WINDOW, and CLOSE — has been implemented to carry multiple logical Telegram connections through a single WebView transport.

On the server side, a dedicated relay receives this stream, separates the individual connections, and forwards them to a regular MTProxy. The relay does not decrypt the MTProxy traffic and does not receive an arbitrary destination address from the client.

The WEB Proxy can also run on a regular HTTPS domain. Such a domain can simultaneously host a normal website, while a special bridge page is opened only after capability verification based on the proxy configuration.

In other words, Telegram is preparing another way to connect to Telegram — through a WebView-based HTTPS/WebSocket transport, while keeping standard MTProxy traffic inside it.