Would you like to discuss your environment with a knowledgable engineer?
First of all, you’d need to set website name. Open /etc/aicache/aicache.cfg and find “website” section in the example configuration file and edit it. For example:
For sites that can not be matched to any of hostname, cname or wildcard values in configuration file, aiScaler returns error “409 Webiste not found”.
Origins are your primary application servers, which aiScaler accelerates. You must add at least one.
For more configuration options see aiScaler Administrator Guide.
Simple test to see if aiScaler is running
Point your browser to the address of your server and add /aiscalerhelp, for example ipadres/aiscalerhelp or -for AWS servers- xx-xx-xx-xx-xxx.compute-1.amazonaws.com/aiscalerhelp. If aiScaler has started correctly, you should see an HTML page, displaying a “help reference”. After you have changed the settings at your DNS provider, this should work for your domain name too, for example: http://www.cnbc.com/aiscalerhelp or http://www.woot.com/aicachehelp (aicache for older versions)
aiScaler allows to cache POST requests just the same way as GETs, although you must be extra careful not to allow caching of private information.
pattern \.html$ regexp 1m request_type post ## only post caching
pattern \.html$ regexp 1m request_type both ## post and get caching
For a POST request to be cacheable, the following criteria must be satisfied:
Then it’s also important to define your content type header. To distinguish various POST requests “Content-Type: application/x-www-form-urlencoded” header must be present along with “param1=value1¶m2=value2..” name/value pairs in the body . Alternatively, MD5 hashing could be run on POST body to create a signature and then appended to URL. ie. /post.php?md5sig=8767864ADFC34678565
Full configuration example with DoS protection, SSL and caching