i know that 1.3.x is development version, but is it stable enough to be
used
in production? as stated here:
Tell me if i figured that right : if the 1.2.x is based on 1.2.0 - then
its
basic functionality is about 1 year old, and the main changes in it are
bug
fixes and few features taken from 1.3 after thorough testing ?
My main goal of course is to use the latest stable version , and i saw
many
bug fixes in 1.3 that did not enter the stable 1.2 branch (such as in
1.3.16
On Sun, Apr 21, 2013 at 09:31:52AM -0400, gadh wrote:
subrequest fixes)
Generally both development aka mainline and stable versions are ok
for production. Development might need a bit more attention on
upgrades though, especially if you use 3rd party modules - as it
occasionally introduces various changes (including API ones).
thanks, where can i see the API changes between 1.2.x and 1.3.x ? i
currently use subrequest in 1.2.8 and in 1.3.16 the filter module is not
called and the browser waits forever (so it does not go to backend also)
On Tue, Apr 23, 2013 at 04:12:14AM -0400, gadh wrote:
thanks, where can i see the API changes between 1.2.x and 1.3.x ? i
currently use subrequest in 1.2.8 and in 1.3.16 the filter module is not
called and the browser waits forever (so it does not go to backend also)
All commits can be seen in nginx source code repository. Commit
logs usually indicate API changes done, either explicitly or
implicitly.
Note though that not everything you can do with nginx internal
structures is a part of the API. And in many cases “it now waits
forever” problems are results of code worked in previous versions
by chance or due to some implementation details which were changed
in new versions.