Matches a new content rule that contains the current service, even if a different service is specified by the content rule. Does not match a content rule, but a previous content rule match connected the client to the current service. This CSS behavior is known as content rule persistence. When using transparent caches, which pre-fetch content, or mirrored content servers, this scheme works because the same content is available on each service. The persistent command in content configuration mode maintains a persistent connection with a server as long as the above criteria is met.
Persistence is enabled by default.
Adding a sorry server to a content rule. The CSS redirects a request for content on a persistent connection if it matches a new content rule that does not contain the current service, or if persistence is disabled and there is a better service configured in the rule. The CSS redirects or remaps the current connection to a new service based on the persistence reset command setting if the command is configured. If the persistence reset command is not configured, the CSS performs a HTTP redirect by default. In this case, the CSS typically sends the content request to the origin server.