Apache2 on Linux Operating Systems (Ubuntu/Debian). (NginX only for existing setups, also limited support)
Multiprocessing Module (MPM): Event, Prefork, Worker
~500-1200 HTTP(S) request per second
With no load-balancer / reverse proxy infrastructure in place, our servers (depending on used hardware) can approx. handle 500-1200 request per seconds. This number is relative as many webapplications are unique. We always recommend a reverse proxy in place, to offload many security related features, which saves a lot of CPU cycles.
HTTP/1.1 and HTTP/2
HTTP/2 offers latency reduction and generally improves performance for webservers. We always, if possible use HTTP/2 for our webservers unless the webapplication is not thread safe (It requires the mpm_worker module). As a fallback solution HTTP/1.1 is used
Should not even be mentioned anymore at this time. The only difference we have, is that we prevent downgrade attacks and other vulnerability involved TLS connections. We only use certificates issued by Let’s Encrypt which come with zero cost for the client and offer the same security.
HTTP Security Headers
Greatly improve the security of your webapplication and allow the webserver to communicate with your clients in a secure and manner and also depending on the header; increase privacy. We put a lot of emphasis on these security headers but very complex web application may not be able to make use of few.
- HTTP-Strict-Transport-Security (HSTS)
- Content-Security-Policy (CSP)
Experienced with the use of most modules, such as for example mod_rewrite (instantly rewrite URL’s based on the client request) and many others.
Only theoritcal knowledge: HTTP/3
Limited support with nginX