What Are the Differences Between Tunnel Resources and Web Resources?
Supported Architectures Differ
Tunnel resources support both B/S (browser/server) and C/S (client/server) architecture applications.
Web resources support only B/S (browser/server) architecture applications.
Different Access Methods
The iOA client must be installed for tunnel resources, and they can be accessed only through the service backend address.
Web resources do not require client installation. You can access services through a browser or other methods, and access is supported through frontend addresses or custom domain names.
Different Address Types for Access
Tunnel resources can only be accessed through the service backend address. When a client accesses the resources, traffic is typically routed by the local virtual NIC to the secure proxy gateway, which is transparent to users.
Agentless proxy Web resources: Access is supported through frontend addresses or custom domain names, while direct access through backend addresses is prohibited. This approach provides a user-friendly access entry point while hiding backend details to enhance security.
Summary of Key Differences
Architecture compatibility: Tunnel resources can adapt to more complex C/S architecture applications, such as traditional desktop clients, while Web resources are only suitable for web-based applications.
Access threshold: Tunnel resources require a client and are suitable for strict control scenarios, while Web resources have zero client dependency and are suitable for quick access.
Why Are Web Resources Not Displayed in the Client?
Web resources are designed for clientless scenarios and are currently not supported for delivery to the client homepage.
How to Configure a Custom Domain Name for a Web Resource?