Why not just turn off buffering completely?by bkosborne - Nginx Mailing List - English
Hmm okay, so that would essentially buffer as much as it can in RAM (which really wouldn't be much based on the default buffer sizes). Once that in memory buffer becomes full, then what happens? It starts sending the data to the client thats in the buffer as well any anything that isn't?by bkosborne - Nginx Mailing List - English
One thing I thought of is that proxy_buffering is ideal if you have slow clients - where downloading the media files could take a long time. In this case, the goal would be to free up upstream workers. However, since my upstream is NOT an application server, and just nginx, is that really necessary? Only thing I can think of there is that it could be bad to keep all those "slow" conneby bkosborne - Nginx Mailing List - English
I'm working on a configuration for an nginx proxy that splits requests between two upstream servers. The main reason I'm using a proxy is for SSL termination and for redundancy between the two upstream servers. Each upstream server is just a simple nginx server with identical media files stored on each. The largest media file requested is around 2.5 megabytes. There are files larger than that,by bkosborne - Nginx Mailing List - English
Anyone? I see there are two different changelogs. http://nginx.org/en/CHANGES-1.2 http://nginx.org/en/CHANGES Why? Why aren't the 1.2.x versions listed in the main changelog?by bkosborne - How to...
So, I'm trying to make heads and tails of the different nginx verisons. On the download page (http://nginx.org/en/download.html), I see that 1.4.1 is the current stable version, and 1.2.9 is the most recent legacy version. Looking at the changelog for 1.4.1, I see it actually includes changes for 1.3 versions as well as 1.2.0. Why wouldn't there be a separate version "branch" for 1by bkosborne - How to...