Hello community, here is the log from the commit of package nginx-module-sticky-ng for openSUSE:Factory checked in at 2018-07-31 16:02:41 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/nginx-module-sticky-ng (Old) and /work/SRC/openSUSE:Factory/.nginx-module-sticky-ng.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Package is "nginx-module-sticky-ng" Tue Jul 31 16:02:41 2018 rev:3 rq:626462 version:0.0.0+git08092016.MACRO Changes: -------- --- /work/SRC/openSUSE:Factory/nginx-module-sticky-ng/nginx-module-sticky-ng.changes 2018-07-25 16:12:14.749820634 +0200 +++ /work/SRC/openSUSE:Factory/.nginx-module-sticky-ng.new/nginx-module-sticky-ng.changes 2018-07-31 16:02:45.467888859 +0200 @@ -1,0 +2,5 @@ +Fri Jul 27 10:27:53 UTC 2018 - jengelh@inai.de + +- Compact description a little. + +------------------------------------------------------------------- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ nginx-module-sticky-ng.spec ++++++ --- /var/tmp/diff_new_pack.Sp7VO5/_old 2018-07-31 16:02:46.103889942 +0200 +++ /var/tmp/diff_new_pack.Sp7VO5/_new 2018-07-31 16:02:46.107889949 +0200 @@ -55,22 +55,16 @@ A nginx module to add a sticky cookie to be always forwarded to the same upstream server. -When dealing with several backend servers, it's sometimes useful that one client -(browser) is always served by the same backend server (for session persistance -for example). - -Using a persistance by IP (with the ip_hash upstream module) is maybe not a good -idea because there could be situations where a lot of different browsers are -coming with the same IP address (behind proxies)and the load balancing system -won't be fair. - -Using a cookie to track the upstream server makes each browser unique. +When dealing with several backend servers, it's sometimes useful that one +client (browser) is always served by the same backend server (for session +persistance for example). A cookie is used to track the upstream server, since +balancing just by IP address, behind which multiple clients may live, can be +unfair to the load balancing. +The Sticky module can't apply when cookies are not supported by the browser. When the sticky module can't apply, it switchs back to the classic Round Robin Upstream or returns a "Bad Gateway" (depending on the no_fallback flag). -Sticky module can't apply when cookies are not supported by the browser. - %prep mkdir %{project_name} tar -xzf %{SOURCE0} --strip-components=1 -C %{project_name}