Broken for NGINX 1.7.4

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Try to apply patch to NGINX 1.7.4
2.
3.

What is the expected output? What do you see instead?

Success.  

nginx-1.7.4

patching file src/http/ngx_http_upstream.c
Hunk #1 succeeded at 4852 (offset 1010 lines).
Hunk #2 succeeded at 4951 (offset 1016 lines).
Hunk #3 succeeded at 4968 (offset 994 lines).
Hunk #4 succeeded at 5005 (offset 994 lines).
Hunk #5 FAILED at 4044.
Hunk #6 succeeded at 5082 (offset 1009 lines).
1 out of 6 hunks FAILED -- saving rejects to file 
src/http/ngx_http_upstream.c.rej
patching file src/http/ngx_http_upstream.h
Hunk #1 succeeded at 93 (offset 8 lines).
Hunk #2 succeeded at 107 (offset 8 lines).

What version of the product are you using? On what operating system?

CentOS 6.5 Linux kernel 2.6.32-431.17.1.el6.x86_64

Please provide any additional information below.

Original issue reported on code.google.com by nathan.durbin on 29 Aug 2014 at 7:42

[GoogleCodeExporter]

I don't know about 1.7.4, but I have modified the patch to work against 1.6.0.
See attached.  (Note: one minor tweak to the original: allows weight=0.  This 
makes it possible to use this functionality for rolling upgrades.  Requests 
with an old cookie will resolve to a server even if its weight is 0, but that 
server will not be used for new sessions, since servers with weight 0 are 
skipped during round robin).

Original comment by d...@classprep.net on 19 Jan 2015 at 4:29

Attachments:

• jvm_route-1.6.0.patch

[GoogleCodeExporter]

I've verified that the patch I supplied for 1.6.0 also can be applied to 1.7.9 
(although I didn't try building or running with it).

Original comment by d...@classprep.net on 19 Jan 2015 at 5:16