Network Integration - concurrentlabs/laguna GitHub Wiki

Laguna integrates with the operator’s network via an optical network tap or a mirrored switch port providing traffic to a network interface monitored by Laguna. This tap is an interface on a network switch, and the “tapping” can be done anywhere in the network where Internet traffic can be accessed.

The purpose of the tap is to relay this client IP request traffic to Laguna. This relay occurs in parallel to the outbound transfer of the traffic to the Internet.

Laguna monitors the traffic to determine if the request is for potentially cacheable content, based upon the cache definition profiles provisioned on Laguna. If the request matches the potentially cacheable criteria, Laguna sends an HTTP 302 redirect to the client, directing it to the Traffic Router for the requested content; Laguna also terminates the client-origin connection by sending resets to the origin. Once the Traffic Router receives the redirected client request it will select an available Apache Traffic Server edge cache instance and then redirect the client to the Apache Traffic Server edge cache. The client typically remembers the redirection so subsequent requests for data within the same session go direct to the edge cache.

Client authentication request exchanges are not handled by Laguna or the transparent caching system, so once the first data request is seen, the business logic will already have been validated by the internet site. This ensures that only valid requests are cached and provided by the transparent cache system.