Some slides: [https://github.com/alifornia/data/blob/master/Data_Science.pptx]
This report shows the historical trends in the usage of web servers since January 2010.
The summary as of now:
| 2010 1 Jan | 2011 1 Jan | 2012 1 Jan | 2013 1 Jan | 2014 1 Jan | 2015 1 Jan | 2016 1 Jan | 2017 1 Jan | 2018 1 Jan | 2019 1 Jan | 2019 7 Oct | |
| Apache | 71.5% | 69.7% | 66.7% | 63.9% | 64.8% | 58.8% | 55.5% | 50.9% | 47.8% | 44.6% | 44.0% |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Nginx | 3.9% | 5.9% | 10.1% | 14.1% | 15.6% | 22.9% | 26.7% | 32.1% | 36.4% | 40.7% | 30.7% |
| Cloudflare Server | 11.2% | ||||||||||
| Microsoft-IIS | 20.6% | 20.1% | 18.4% | 16.8% | 14.6% | 13.3% | 12.4% | 11.6% | 10.5% | 9.0% | 8.2% |
| LiteSpeed | 0.6% | 1.0% | 1.4% | 1.8% | 2.0% | 2.1% | 2.3% | 2.3% | 3.1% | 3.7% | 4.7% |
| Google Servers | 0.6% | 0.7% | 1.0% | 1.3% | 1.3% | 1.3% | 1.4% | 1.3% | 1.0% | 0.9% | 1.0% |
| Node.js | <0.1% | <0.1% | 0.1% | 0.1% | 0.2% | 0.2% | 0.4% | 0.6% | 0.7% | ||
| Apache Traffic Server | <0.1% | 0.2% | 0.2% | 0.3% | 0.3% | 0.4% | 0.5% | ||||
| Tomcat | 0.6% | 0.6% | 0.6% | 0.7% | 0.4% | 0.4% | 0.5% | 0.6% | 0.5% | 0.4% | 0.2% |
| IdeaWebServer | 0.3% | 0.3% | 0.3% | 0.3% | 0.2% | ||||||
| Cowboy | 0.1% | 0.1% | 0.1% | 0.1% | 0.1% | 0.1% | |||||
| Tengine | 0.1% | 0.2% | 0.1% | 0.1% | 0.2% | 0.1% | 0.1% | ||||
| Kestrel | <0.1% | 0.1% | 0.1% | ||||||||
| Lighttpd | 0.6% | 0.6% | 0.6% | 0.5% | 0.3% | 0.2% | 0.1% | 0.1% | 0.1% | 0.1% | <0.1% |
| Oracle Servers | 0.1% | 0.1% | 0.2% | 0.2% | 0.1% | 0.1% | 0.1% | 0.1% | <0.1% | <0.1% | <0.1% |
| Zope | 0.1% | 0.1% | 0.1% | 0.1% | 0.1% | <0.1% | <0.1% | <0.1% | <0.1% | <0.1% | <0.1% |
| IBM Servers | 0.4% | 0.3% | 0.3% | 0.3% | 0.2% | 0.1% | 0.1% | 0.1% | <0.1% | <0.1% | <0.1% |
| Jetty | 0.1% | 0.1% | 0.1% | <0.1% | 0.1% | 0.1% | <0.1% | <0.1% | <0.1% | <0.1% | <0.1% |
| Resin | 0.1% | 0.1% | 0.1% | 0.1% | 0.1% | <0.1% | <0.1% | <0.1% | <0.1% | <0.1% | <0.1% |
| Zeus | 0.2% | 0.1% | 0.1% | 0.1% | 0.1% | <0.1% | <0.1% | <0.1% | <0.1% | <0.1% | <0.1% |
| Mongrel | 0.1% | 0.1% | <0.1% | <0.1% | <0.1% | <0.1% | <0.1% | <0.1% | <0.1% | <0.1% | <0.1% |
| Yahoo Traffic Server | 0.3% | 0.2% | 0.3% | 0.2% | 0.3% | <0.1% | <0.1% | <0.1% | <0.1% | <0.1% | |
| Sun Servers | 0.2% | 0.2% |
- The HTTP protocol does not specify a limit.
- The POST method allows sending far more data than the GET method, which is limited by the URL length - about 2KB.
- The maximum POST request body size is configured on the HTTP server and typically ranges from
1MB to 2GB - The HTTP client (browser or other user agent) can have its own limitations. Therefore, the maximum POST body request size is
min(serverMaximumSize, clientMaximumSize).
Here are the POST body sizes for some of the more popular HTTP servers:
- Ngix (largest web server market share as of April 2019) - default 1MB, no practical maximum (2**63)
- Apache - maximum 2GB, no default documented
- IIS - default 28.6MB for the request length, 2048 bytes for the query string; maximum undocumented
- InfluxDB - default ~25MB, maximum undocumented