What behavior does non-80 and non-443 traffic exhibit in Z-Tunnel 1.0?

The behavior of non-80 and non-443 traffic in Z-Tunnel 1.0 is that it bypasses the Zscaler Client Connector. In this scenario, traffic that does not use the standard web ports (HTTP and HTTPS) is typically not directed through the Zscaler service, which means it does not get the same level of inspection or security applied by the Zscaler platform. This is intentional, as Z-Tunnel primarily focuses on traffic that passes through the common web ports for optimal functionality and security enforcement.

This straightforward handling of non-standard traffic is crucial for understanding how Zscaler manages diverse types of network traffic and ensures that the resources within the organization can remain reachable without unnecessary delays or interruptions. When data travels through non-standard ports, organizations often have specific needs or use cases in mind, which might necessitate different routing or handling practices that do not align with the Zscaler framework designed for standard web traffic.

In contrast, the other behaviors mentioned do not accurately represent non-80 and non-443 traffic behavior in the context of Z-Tunnel 1.0. For example, this traffic does not get encrypted by the tunneling process or routed through Zscaler servers, nor is it automatically blocked. Instead