Tenzir nodes now honor standard HTTP proxy environment variables when connecting to the Tenzir Platform, and hash functions produce correct checksums for binary values.
🚀 Features
Section titled “🚀 Features”Platform websocket proxy support
Section titled “Platform websocket proxy support”Apr 16, 2026 · @tobim, @codex · #6039
Tenzir nodes now honor standard HTTP proxy environment variables when connecting to Tenzir Platform:
HTTPS_PROXY=http://proxy.example:3128 tenzir-nodeUse NO_PROXY to bypass the proxy for selected hosts. This helps deployments where outbound connections to the Platform websocket gateway must go through an HTTP proxy.
🔧 Changes
Section titled “🔧 Changes”Add accept_http operator for receiving HTTP requests
Section titled “Add accept_http operator for receiving HTTP requests”Apr 15, 2026 · @lava
We added a new operator to accept data from incoming HTTP connections.
The server option of the from_http operator is now deprecated.
Going forward, it should only be used for client-mode HTTP operations,
and the new accept_http operator should be used for server-mode
operations.
🐞 Bug Fixes
Section titled “🐞 Bug Fixes”Raw-byte hashing for binary values
Section titled “Raw-byte hashing for binary values”Apr 16, 2026 · @mavam, @codex · #6022
The hash_* functions now hash blob values by their raw bytes. This makes checksums computed from binary data match external tools such as md5sum and sha256sum.
For example:
from_file "trace.pcap" { read_all binary=true}md5 = data.hash_md5()This is useful for verifying file contents and round-tripping binary formats without leaving TQL.