CLI: Edge Cache Acceleration

You can use the acceleration edge-cache command to configure Edge Cache acceleration. Edge Cache enables single-sided caching of Internet-based content, including web objects, videos and software updates. Edge Cache requires only one Exinda appliance.

When web objects are downloaded from the Internet or across WANWide Area Network links, Edge Cache stores them at the edge of the network. When subsequent requests come for the same material, the content is quickly delivered from Edge Cache, without the need to re-download the data over the WAN. The result is the ability to experience LANLocal area network speeds of WAN objects, and provide users with a better network experience.

Edge Cache also supports HTTPS sites allowing the appliance to be a forward proxy and decrypt content for caching. This is important as more and more applications and services are moving to the cloud. These SaaS-based applications are typically delivered over HTTPS and so to be effective, Edge Cache must support caching this HTTPS traffic.

Configuring Edge Cache

To specify the maximum and minimum size of objects to store:

acceleration edge-cache object-size {maximum|minimum> <size>

• <size> – The size parameter should use SI units e.g. 100M or 512k.

To specify how long Edge Cache should wait for a response when fetching objects from the server:

acceleration edge-cache connect-timeout <seconds>

To add or remove an HTTP URL or domain that should be blacklisted (i.e. should never be cached):

[no] acceleration edge-cache never-cache <URL or domain>

To add or remove HTTP applications that should be cached:

[no] acceleration edge-cache application <application>

• application <application> - Only applications that use the HTTP protocol are supported.

To enable [or disable] HTTPS caching:

[no] acceleration edge-cache enable-https

To specify the signing certificate to use to create dynamic SSL certificates during HTTPS caching:

acceleration edge-cache https-cert <cert-name>

To specify an HTTPS black-list of IPs or domains:

acceleration edge-cache https-list-type black-list

Specifies that Edge Cache will use a black-list for determining what sites can not be cached. All others will be allowed.

acceleration edge-cache https-black-list {dest-domain|dest-ip|src-domain|src-ip}

• src-domain <domain> - The domain that initiated the conversation.
• src-ip <ip> - The IPInternet protocol that initiated the conversation. The IP can include a mask.
• dest-domain <domain> - The domain that was the destination of the conversation.
• dest-ip <ip> - The IP that was the destination of the conversation. The IP can include a mask.
• Note: Domains are resolved using the DSN. Ensure the domains are in the format that are required by DNSDomain Name Server (i.e. without https://)

To remove a domain or IP from the black-list:

no acceleration edge-cache https-black-list <internal ID>

https-black list <internal ID> – To determine the internal ID, type: no acceleration edge-cache https-black-list ?, which presents the list of HTTPS black-list sites in the format: Internal ID, Type, Value

To specify an HTTPS white-list of IPs or domains:

acceleration edge-cache https-list-type white-list

• Specifies that Edge Cache will use a white-list for determining what sites can be cached. No others will be allowed.

acceleration edge-cache https-white-list {dest-domain|dest-ip|src-domain|src-ip}

• src-domain <domain> - The domain that initiated the conversation.
• src-ip <ip> - The IP that initiated the conversation. The IP can include a mask.
• dest-domain <domain> - The domain that was the destination of the conversation.
• dest-ip <ip> - The IP that was the destination of the conversation. The IP can include a mask.
• Note: Domains are resolved using the DSN. Ensure the domains are in the format that are required by DNS (i.e. without https://)

To remove a domain or IP from the white-list:

no acceleration edge-cache https-white-list <internal ID>

• https-white list <internal ID> - To determine the internal ID, type: no acceleration edge-cache https-white-list ?, which presents the list of HTTPS whit-list sites in the format: Internal ID, Type, Value

To clear the object cache:

acceleration edge-cache cache clear

To configure an Edge Cache peer:

If you have an upstream proxy in your environment, you can configure it as a proxy peer to ensure that Edge Cache can fetch content from the Internet.

[no] acceleration edge-cache peer <hostname> [http-port|icp-port|option]

• <hostname> - The hostname of the peer object memory.
• http-port <port> - The HTTP port for the peer command
• icp-port <port> - The ICP port for the peer command
• option default - Use the default peer options
• option proxy-only - Do not cache objects from this peer.
• option no-query - This peer does not support ICP
• option weight=n - Specify the peer priority. Peers with higher priority will be consulted first.
• option round-robin - Specify that peers should be consulted in round-robin order.
• option closest-only - Only forward closest parent ICP misses.
• option originserver - Specify that this peer is an origin server

To never fetch a file directly; always use the peer:

[no] acceleration edge-cache never-direct

To prevent delays when skipping ahead during video downloads:

acceleration edge-cache range-offset <limit>

Viewing configuration settings

To show the current Edge Cache configuration settings:

show acceleration edge-cache

For more information, see to the Edge Cache How To Guide.