Exinda EXNV-10063, Руководство администратора

Страница: 501 / 623

Exinda Network Orchestrator 4 Settings | 501
web object from Edge Cache as if it were the server. Edge Cache then requests the web object from the server over its
previously established trusted connection. The server provides the content to Edge Cache, which then stores the
content, if applicable. The connection with the server can be closed. Edge Cache then serves the content to the client
and the connection with the client can then be closed.
Screenshot 188: Sequence of operations for caching encrypted traffic using Edge Cache
When determining whether the content should be stored in the cache, Edge Cache evaluates whether it is the
appropriate size and whether it is white- or black-listed. The whitelist and blacklist can consist of source IP, destination IP,
source domain, and destination domain. Note that the domains are resolved using DNS, so the resulting IP addresses are
reverse mapped to determine the domain that is used to configure the Edge Cache engine.
The next time a client requests the same content, the same negotiation happens where the client requests a secure
communication channel with the server, the Exinda appliance intercepts and forms a secure communication channel
with the server, forges the certificate and establishes a secure communication channel with the client (on behalf of the
server). The client then requests the specific web content. Edge Cache determines that the requested content is
available in cache and serves it to the client. Edge Cache then closes the communication channels with both the server
and the client.