An introduction to web cache proxy server - nuster

       0

We aggregate and tag open source projects. We have collections of more than one million projects. Check out the projects section.

An introduction to web cache proxy server - nuster

Nuster is a simple yet powerful web caching proxy server based on HAProxy. It is 100% compatible with HAProxy, and takes full advantage of the ACL functionality of HAProxy to provide fine-grained caching policy based on the content of request, response or server status. This article gives an overview of nuster - web cache proxy server, its installation and few examples of how to use it.

Its features include:

• All features of HAProxy are inherited, 100% compatible with HAProxy
• Powerful dynamic cache ability
  • Based on HTTP method, URI, path, query, header, cookies, etc
  • Based on HTTP request or response contents, etc
  • Based on environment variables, server state, etc
  • Based on SSL version, SNI, etc
  • Based on connection rate, number, byte, etc
• Extremely fast
• Cache purging
• HTTPS supports on both frontend and backend
• HTTP compression
• HTTP rewriting and redirection

Installation

make TARGET=linux2628 USE_LUA=1 LUA_INC=/usr/include/lua5.3 USE_OPENSSL=1 USE_PCRE=1 USE_ZLIB=1
make install PREFIX=/usr/local/nuster/bin
TARGET: linux2628, linux26, linux24, linux24e, linux22, solaris, freebsd, openbsd, cygwin, custom, generic

docker pull nuster/nuster
docker run -d -v /path/to/nuster.cfg:/etc/nuster/nuster.cfg:ro -p 8080:8080 nuster/nuster

Minimal config file:

Section description: 

• global: global parameters
• defaults: default parameters for proxy section
• frontend: parameter for frontend which accept requests from client
• backend: forward requests to backend servers
• listen: combine frontend and backend

frontend mysql-lb
   bind *:3306
   mode tcp
   default_backend mysql-cluster
backend mysql-cluster
   balance roundrobin
   mode tcp
   server s1 10.0.0.101:3306
   server s2 10.0.0.102:3306
   server s3 10.0.0.103:3306 

              

As HTTP Load Balancer:

frontend web-lb
   bind *:80
   mode http
   default_backend apps
backend apps
   balance roundrobin
   mode http
   server s1 10.0.0.101:8080
   server s2 10.0.0.102:8080
   server s3 10.0.0.103:8080

As HTTPS Load Balancer:

frontend web
    bind *:8080 ssl crt XXX.pem
    # bind *:8080
    mode http
    default_backend app
backend app
    balance roundrobin
    filter cache off
    cache-rule all
    mode http
    #server a1 10.0.0.101:8002
    server a2 10.0.0.101:8003 ssl verify none

Web caching

frontend web1
    bind *:8080
    mode http
    use_backend app1a if { path /search }
    default_backend app1b
backend app1a
    balance roundrobin
    mode http
    option http-buffer-request
    filter cache
    cache-rule rpost ttl 60 if METH_POST
backend app1b
    #***

cache /a.jpg, no expire

cache-rule r1 ttl 0 if { path /a.jpg }

acl static path_beg -i /static/ /images/ /css/
cache-rule static_files ttl 0 if static

acl pathB path /mypage
cache-rule r2 key method.scheme.host.path.delimiter.query.cookie_sessionId ttl 60 if pathB

http-request set-var(txn.pathC) path
acl pathC var(txn.pathC) -m str /a.html
acl resHdrCache1 res.hdr(cache) yes

cache-rule r3 if pathC resHdrCache1

acl heavypage path /heavy
acl tooFast be_conn ge 100
cache-rule heavy ttl 100 if heavypage tooFast

 

http-response set-header X-ASDF fdsa

backend app
  filter compression
  compression algo gzip
  compression type text/html text/plain text/css text/javascript
  filter cache
  cache-rule all

curl -XPURGE https://127.0.0.1/imgs/test.jpg

 

If you define cache purge-method MYPURGE in global, you can use

curl -XMYPURGE https://127.0.0.1/imgs/test.jpg