This shows you the differences between the selected revision and the current version of the page.
|
litespeed_wiki:reverse_proxy_cache 2012/11/21 14:21 |
litespeed_wiki:reverse_proxy_cache 2012/11/26 04:15 current |
| | 5b. Set up cache policy at vhost Level | | 5b. Set up cache policy at vhost Level |
| | {{ http://i49.tinypic.com/2i7v3h5.png?700 |vhost cache policy}} | | {{ http://i49.tinypic.com/2i7v3h5.png?700 |vhost cache policy}} |
| | + | |
| | | | |
| | | | |
| | - The set up has been tested and worked on a production server running varnish+nginx+tomcat+postgresql, being able to defend 20000 requests/sec HTTP ddos attacks (with LiteSpeed Advance Anti-DDoS setup). | | - The set up has been tested and worked on a production server running varnish+nginx+tomcat+postgresql, being able to defend 20000 requests/sec HTTP ddos attacks (with LiteSpeed Advance Anti-DDoS setup). |
| | - Above setup can be easily extended to support proxy'ing multiple backends with each vhost (with its own web server type context) per each backend. | | - Above setup can be easily extended to support proxy'ing multiple backends with each vhost (with its own web server type context) per each backend. |
| - | - Above setup also can be easily extended to support load balancing multiple backends by creating a loadbalancer context at vhost level based on a loadbalancer external app (server or vhost level) with proxy::backend* as its worker. | + | - Above setup also can be easily extended to support load balancing multiple backends by creating a loadbalancer context at vhost level based on a loadbalancer external app (server or vhost level) with proxy::backend* being its worker. |
| | | | |
