Faq - Revision history

Andyvlx at 10:37, 7 June 2012

2012-06-07T10:37:44Z

Andyvlx at 10:37, 7 June 2012

2012-06-07T10:37:00Z

Andyvlx at 10:36, 7 June 2012

2012-06-07T10:36:04Z

Andyvlx at 10:28, 7 June 2012

2012-06-07T10:28:01Z

Andyvlx at 10:27, 7 June 2012

2012-06-07T10:27:38Z

Andyvlx at 10:27, 7 June 2012

2012-06-07T10:27:10Z

Andyvlx at 10:24, 7 June 2012

2012-06-07T10:24:33Z

Malan: /* How do I generate an .htpasswd file without having Apache tools installed? */

2012-02-15T11:42:57Z

‎How do I generate an .htpasswd file without having Apache tools installed?

Malan: /* How do I generate an .htpasswd file without having Apache tools installed? */

2012-02-15T11:42:11Z

‎How do I generate an .htpasswd file without having Apache tools installed?

Malan: /* How do I generate an .htpasswd file without having Apache tools installed? */

2012-02-15T09:52:39Z

‎How do I generate an .htpasswd file without having Apache tools installed?

← Older revision		Revision as of 10:37, 7 June 2012
Line 101:		Line 101:

	Nginx is not a virus. Please check a detailed description here:		Nginx is not a virus. Please check a detailed description here:
−	* [http://nginx.org/en/docs/welcome_nginx_facebook.html]	+	* [http://nginx.org/en/docs/welcome_nginx_facebook.html Welcome to nginx!]

← Older revision		Revision as of 10:37, 7 June 2012
Line 101:		Line 101:

	Nginx is not a virus. Please check a detailed description here:		Nginx is not a virus. Please check a detailed description here:
−	* [[http://nginx.org/en/docs/welcome_nginx_facebook.html~~\|nginx.org frequently asked questions]~~]	+	* [http://nginx.org/en/docs/welcome_nginx_facebook.html]

← Older revision		Revision as of 10:36, 7 June 2012
Line 96:		Line 96:

	Note: Many users have requested that Nginx implement a feature in the load balancer to limit the number of requests per backend (usually to one). While support for this is planned, it's worth mentioning that demand for this feature is rooted in misbehaviour on the part of the application being proxied ''to'' (Ruby on Rails seems to be one example). This is not an Nginx issue. In an ideal world, this particular problem fix request would be directed toward the backend application and its ability handle simultaneous requests.		Note: Many users have requested that Nginx implement a feature in the load balancer to limit the number of requests per backend (usually to one). While support for this is planned, it's worth mentioning that demand for this feature is rooted in misbehaviour on the part of the application being proxied ''to'' (Ruby on Rails seems to be one example). This is not an Nginx issue. In an ideal world, this particular problem fix request would be directed toward the backend application and its ability handle simultaneous requests.
		+
		+	= Miscellaneous =
		+	== Why do I see "Welcome to nginx!" when I'm trying to access Facebook, Yahoo!, Google or some other well-known website? Is nginx a virus? ==
		+
		+	Nginx is not a virus. Please check a detailed description here:
		+	* [[http://nginx.org/en/docs/welcome_nginx_facebook.html\|nginx.org frequently asked questions]]

@@ Line 11: / Line 11: @@
 == Is it safe to use the development branch in production? ==
-In general, all releases (development or otherwise) are quite stable.  This site runs the latest development version at all times.  Many nginx users tend to represent an "early adopter" crowd, so a large segment is using the bleeding edge version at any given point.  The major and most important point about development version is that it can occasionally break APIs for 3rd party modules (APIs are sometimes changes in the development branch).  Other than that, it gets all non-emergency bugfixes first.
+In general, all releases (development or otherwise) are quite stable.  This site runs the latest development version at all times.  Many nginx users tend to represent an "early adopter" crowd, so a large segment is using the bleeding edge version at any given point.  The major and most important point about development version is that it can occasionally break APIs for 3rd party modules (APIs are sometimes changed in the development branch).  Other than that, it gets all non-emergency bugfixes first.
 That said, if stability is crucial it is best to briefly hold off on deployment after a development release; critical bugs tend to show up within the first couple days (which often results in another release immediately afterwards).  If no new release shows up in two or three days, then it's likely no one has found any critical bugs. In the event that you discover a bug, capture a debug log and submit a descriptive bug report!

@@ Line 11: / Line 11: @@
 == Is it safe to use the development branch in production? ==
-In general, all releases (development or otherwise) are quite stable.  This site runs the latest development version at all times.  Nginx users as a whole tend to represent an "early adopter" crowd, so a large segment is using the bleeding edge version at any given point.  The major and most important point about development version is that it can occasionally break APIs for 3rd party modules (APIs are sometimes changes in the development branch).  Other than that, it gets all non-emergency bugfixes first.
+In general, all releases (development or otherwise) are quite stable.  This site runs the latest development version at all times.  Many nginx users tend to represent an "early adopter" crowd, so a large segment is using the bleeding edge version at any given point.  The major and most important point about development version is that it can occasionally break APIs for 3rd party modules (APIs are sometimes changes in the development branch).  Other than that, it gets all non-emergency bugfixes first.
 That said, if stability is crucial it is best to briefly hold off on deployment after a development release; critical bugs tend to show up within the first couple days (which often results in another release immediately afterwards).  If no new release shows up in two or three days, then it's likely no one has found any critical bugs. In the event that you discover a bug, capture a debug log and submit a descriptive bug report!

@@ Line 91: / Line 91: @@
 == What algorithm does Nginx use to load balance?  Can it balance based on connection load? ==
-Currently, Nginx uses a simple round robin algorithm.  It cannot balance based on connection load.  (This may change in a future release.)
+Currently, Nginx has round-robin, least connections and ip-hash algorithms (all come with weights).
-There is a third-party module, [[NginxHttpUpstreamRequestHashModule|Http Upstream Hash]], that uses a form of hash load balancing.
+There are also a number of third-party modules for oad balancing.
 Note: Many users have requested that Nginx implement a feature in the load balancer to limit the number of requests per backend (usually to one).  While support for this is planned, it's worth mentioning that demand for this feature is rooted in misbehaviour on the part of the application being proxied ''to'' (Ruby on Rails seems to be one example). This is not an Nginx issue. In an ideal world, this particular problem fix request would be directed toward the backend application and its ability handle simultaneous requests.

@@ Line 18: / Line 18: @@
 * In Linux (or Posix):  given users John, Mary and Jane and passwords V3Ry, SEcRe7, and V3RySEcRe7, in order to generate a password file named .htpasswd, you would issue:
-<pre>printf "John:$(openssl passwd -crypt V3Ry)\n" >> .htpasswd # this example uses '''crypt''' encryption</pre>
+<pre>printf "John:$(openssl passwd -crypt V3Ry)\n" >> .htpasswd # this example uses crypt encryption</pre>
-<pre>printf "Mary:$(openssl passwd -apr1 SEcRe7)\n" >> .htpasswd # this example uses '''apr1 (Apache MD5)''' encryption</pre>
+<pre>printf "Mary:$(openssl passwd -apr1 SEcRe7)\n" >> .htpasswd # this example uses apr1 (Apache MD5) encryption</pre>
-<pre>printf "Jane:$(openssl passwd -1 V3RySEcRe7)\n" >> .htpasswd # this example uses '''MD5''' encryption</pre>
+<pre>printf "Jane:$(openssl passwd -1 V3RySEcRe7)\n" >> .htpasswd # this example uses MD5 encryption</pre>
 TODO: example for SSHA (Salted Secure Hash Algorithm).

@@ Line 17: / Line 17: @@
 == How do I generate an .htpasswd file without having Apache tools installed? ==
-* In Linux (or Posix):  given users named John and Mary and passwords V3Ry and SEcRe7, to generate a password file named .htpasswd, you would issue:
+* In Linux (or Posix):  given users John, Mary and Jane and passwords V3Ry, SEcRe7, and V3RySEcRe7, in order to generate a password file named .htpasswd, you would issue:
-** printf "John:$(openssl passwd -crypt V3Ry)\n" >> .htpasswd # this example uses crypt encryption
+<pre>printf "John:$(openssl passwd -crypt V3Ry)\n" >> .htpasswd # this example uses '''crypt''' encryption</pre>
-** printf "Mary:$(openssl passwd -apr1 SEcRe7)\n" >> .htpasswd # this example uses apr1 (Apache MD5) encryption
+<pre>printf "Mary:$(openssl passwd -apr1 SEcRe7)\n" >> .htpasswd # this example uses '''apr1 (Apache MD5)''' encryption</pre>
 TODO: example for SSHA (Salted Secure Hash Algorithm).

@@ Line 20: / Line 20: @@
 ** printf "John:$(openssl passwd -crypt V3Ry)\n" >> .htpasswd # this example uses crypt encryption
 ** printf "Mary:$(openssl passwd -apr1 SEcRe7)\n" >> .htpasswd # this example uses apr1 (Apache MD5) encryption
-** TODO: example for SSHA (Salted Secure Hash Algorithm).
 * Or, you may use the [http://trac.edgewall.org/browser/trunk/contrib/htpasswd.py htpasswd.py] python script.