soheilhy/cmux

Features

• Single-Port Multi-Protocol Support - Runs several different network services on one IP address and port without needing a dedicated port for each.
• TCP Connection Multiplexers - Provides a TCP connection multiplexer that routes traffic to different listeners based on initial payload content.
• TLS Handshake Detection - Identifies secure connections by matching the TLS handshake packet and filtering by protocol version.
• Connection Multiplexing - Multiplexes multiple network protocols over one TCP port by analyzing the first packet of each connection.
• HTTP/2 Protocol Detection - Detects HTTP/2 connections by analyzing the frame header within the initial data packet.
• HTTP/1 Protocol Detection - Identifies HTTP/1 requests by parsing the method or first line of the connection payload for protocol dispatching.
• Payload-Based Connection Routing - Provides the ability to route TCP connections to different backend handlers by inspecting initial payload bytes.
• Network Traffic Routers - Inspects connection headers and byte prefixes to direct network traffic to specific backend listeners.
• Single-Port Protocol Detection - Acts as a layer four router that identifies protocols like HTTP, TLS, and HTTP/2 to share a single port.
• Protocol Payload Inspectors - Buffers the first few bytes of an incoming stream to analyze protocol signatures before handing off the connection.
• Protocol Detection Forwarders - Identifies incoming traffic such as HTTP or TLS using packet signatures to direct connections to the appropriate backend handler.
• Header-Based Routing - Directs network traffic to specific listeners by parsing and evaluating request headers found in the initial payload.
• Traffic Protocol Inspection - Provides capabilities for detecting and managing network protocols by inspecting initial connection bytes.
• Payload-Based Traffic Filtering - Inspects request headers and payload prefixes to decide which application logic should handle a network connection.
• Protocol Prefix Matching - Identifies target handlers by comparing the initial bytes of a TCP connection against predefined byte sequences.
• Protocol Signature Matching - Identifies incoming traffic using protocol signatures for HTTP or TLS to assign connections to the correct handler.
• Payload - Identifies incoming connections by comparing the initial bytes of the payload against predefined string prefixes.
• Proxy Phase Timeouts - Defines a time limit for the initial read operation that inspects the connection payload during the matching phase.
• Blocking Operation Timeouts - Enforces a strict time limit on the initial read operation to prevent slow connections from blocking the multiplexer.
• Connection Handshake Protocols - Sends data back to the client during the matching process to complete protocol handshakes before final hand-off.
• Custom Handshake Responses - Sends specific data responses to clients during the connection phase before handing the session off to a final protocol handler.
• Fallback Connection Routing - Redirects connections that fail all specific protocol matches to a designated default handler.
• Fallback Protocol Routing - Redirects connections to a fallback handler when no other specific protocol rules match the incoming traffic.
• Concurrent Handshake Writes - Allows a response, such as a TLS handshake, to be sent to the client while simultaneously matching the connection.
• Bidirectional Matching - Provides the ability to send data back to the client while reading bytes to determine the protocol.
• Header-Based Routing - Implements routing logic that directs connections based on specific values found in HTTP request headers.
• Header Prefix Routing - Allows directing network connections based on whether an HTTP header value starts with a specific string.
• Priority-Based Dispatch - Assigns connections to the first configured protocol listener that satisfies the matching criteria based on priority.

Star history