Manage traffic at critical connection points with Traffic Policy phases

The new phase-based approach to ngrok's Traffic Policy engine replaces the previous inbound and outbound directions with phase-specific labels such as on_tcp_connect, on_http_request, and on_http_response, offering more granular control over traffic management. This update allows users to configure actions at specific stages in the connection lifecycle, enhancing clarity and flexibility in handling traffic, particularly for security measures like blocking unwanted connections early at the transport layer or managing TLS termination. The changes include updates to the Traffic Policy API, agent configuration files, SDKs, and the Kubernetes Operator, ensuring greater consistency and ease of management across the platform. Users are encouraged to transition to the new format to leverage these advanced capabilities, as the traditional inbound and outbound phases will eventually be deprecated. The improved system is designed to align with real-world scenarios, providing intuitive and precise traffic management solutions.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.