Hardening your SSL installation
Snapt provides SSL termination/offloading in both the Accelerator and Balancer modules. These are extremely resilient and secure by default, but...
- Home
- Accelerator
Accelerator
-
-
Source IP with X-Forwarded-For
By default, the Load balanced web servers will not see the Clients IP as the actual Source IP from which the request originates, instead... -
Passing the scheme through SSL termination
Often times when you are terminating SSL connections at the Accelerator or the Balancer, you need to know whether the... -
Redirect port 80 to port 443 (HTTP to HTTPS)
There are certain circumstances in which you might want to transparently pass traffic from one port to another. Quite typically... -
Timeouts in Balancer and Accelerator
When Increasing the timeout of connections in the Balancer you must go to Balancer -> Configuration -> Default Settings. In the... -
How to disable SSLv3?
The Accelerator has SSLv3 blocked by force – it cannot be used on it. The Balancer allows SSLv3, but it... -
How do I send Accelerator requests to the Balancer?
If you have the Snapt Balancer installed when you add an Upstream you will automatically be able to choose a... -
Accelerator custom headers
Custom headers(e.g X-Forwarded-For) can be applied through Accelerator->Caching->Cache Profiles You can add custom headers to the Custom Headers[Advanced] Block to have it... -
Custom compile Nginx, Naxsi and PageSpeed
Snapt makes use of a heavily customized compilation of NGINX. While NGINX itself performs quite well out of the box, we implemented... -
worker_connections are not enough
If you have a busy Accelerator you might see a set of errors like this in your log — 2014/01/25...