CAN Frequently Asked Questions

The Commerce Acceleration Network (CAN) platform specializes in improving data delivery performance for sites that deal with database-driven or user-specific content. For example, leveraging CAN to serve social media, online banking, and e-commerce sites will generate significant improvements in web page load times.

Yes. CAN was designed to speed up data delivery from any customer origin server.

It supports the following features:

• HTTPS
• Token-Based Authentication
• Country Filtering
• Rules Engine
• Analytics
• Web Application Firewall (WAF)
• Rate Limiting

The purpose of the CAN Gateway server is to ensure that requests are routed efficiently through our network to your origin server.

CAN Gateway servers assess their ability to communicate with the server(s) associated with a customer origin configuration by requesting the asset specified in the Validation Path option. The results of this query will generate a failover list of the top three CAN Gateway servers, in terms of performance, for the customer origin configuration that triggered this assessment.

This assessment is triggered by any of the following events:

• The creation of a customer origin configuration
• Reset is clicked when viewing or modifying a customer origin configuration

Each customer origin configuration is assigned a failover list of our top performing CAN Gateway servers. This failover list ensures that traffic to your origin server is routed over an optimal path in the unlikely case of CAN Gateway server failure.

A CAN Gateway server may be unavailable as a result of routine maintenance or an unplanned outage. If this occurs to a CAN Gateway server serving traffic for your customer origin configuration, traffic will automatically fail over to the next CAN Gateway server in that customer origin's failover list. Additionally, periodic checks will be performed to see whether the CAN Gateway server in question may resume serving traffic.

Yes. However, due to the dynamic nature of the content typically routed through CAN, caching is turned off by default on this platform. Caching on the CAN platform may be enabled through Rules Engine by disabling the Bypass Cache feature on the desired requests. Make sure that a cache policy is defined for the desired requests either by your web server or through Rules Engine.

Yes. However, purging is unnecessary unless caching has been enabled on the CAN platform.

• Content Delivery

  • CAN
  • IPv6
  • Cache Management
  • Rules Engine

• Security

  • CDN Security
  • TCC Security
  • Token-Based Authentication
  • Web Application Firewall (WAF)
• Raw Logs
• Storage