v0.7.0

TeleGO v0.7.0

High-performance Telegram MTProxy with TLS fronting.

v0.7.0 — WEB WebSocket compatibility with lighttpd

Released 2026-10-13.

WEB WebSocket upgrades

Telego now accepts Connection: close, upgrade in a WebSocket handshake.
Previously, the HTTP parser rejected this combination with HTTP 400 before authentication or WebSocket handshake processing.
This correction supports the request that lighttpd forwards in issue #80.

The parser recognizes Upgrade as a complete token, regardless of case, order, or surrounding spaces and tabs.
This behavior follows RFC 6455 section 4.2.1.
After a successful upgrade, the WebSocket transport controls the connection lifetime.

The correction applies to both websocket and websocket-lanes, including installations that use a WEB base path.
Regression tests cover both handshakes and subsequent data transfer.
Duplicate tokens, unsupported tokens, and an upgrade token without an Upgrade header still cause rejection.
Ordinary HTTP requests with Connection: close retain their existing behavior.

Upgrade

Restart Telego after the binary or container update.
Existing configuration, secrets, and proxy links remain compatible.
This release adds no configuration keys or required frontend changes.

If you upgrade from v0.6.7 or earlier, apply the Nginx fallback correction in the v0.6.8 release notes.

Full changelog: v0.6.9…v0.7.0

Full Changelog: v0.6.9...v0.7.0