NetDNA today announced EdgeRules, an instantaneous HTTP caching rules service, giving site managers rapid and granular control over their web content for a better user experience, improved security, lower bandwidth costs and the ability to better monetize content by preventing hotlinking.
EdgeRules is an add-on service to NetDNA’s EdgeCaching and EdgeCaching for Platforms. Both of these HTTP caching services place site content in NetDNA’s worldwide network of edge servers and peering partners for superior web performance optimization.
Using the EdgeRules control panel, site managers can make changes to their content rules and see them enacted in less than one minute – with no review needed from the NetDNA engineering team. This makes it possible for the first time to test, tweak and deploy very granular controls over how and when content is served.
“EdgeRules truly gives website manages the ability to manage their CDN services their way and to finely tune their pull zone content in a way that they never could before,” said David Henzel, NetDNA vice president of marketing. “NetDNA is well known for giving site managers unprecedented control over their CDN service through our Control Panel. With EdgeRules, we are at the forefront of CDN self provisioning again.”
A site manager can use EdgeRules to keep certain files from being proxied and thus protecting them from exposure on the Internet. For example, EdgeRules can prevent the exposure of directory indices due to misconfiguration, which is a common problem on cloud services such as Amazon’s S3 service.
The service allows different rules to be set for different files or classes of data so that frequently updated files can be classed differently from more static data. This reduces calls to the origin server, which lowers bandwidth charges.
Site managers can also use the service to blacklist certain IP addresses, for example blocking web robots that are scraping data from the site.
The EdgeRules service can also read the operating system of a device and serve up optimized content for that device. For example a smartphone-optimized image can be served up instead of a large image when the service detects a request from an Android or iOS device.