doc: modified the todo section. we now have exit_worker_by_lua (#2009)

Author: chronolaw

README.markdown

@@ -974,7 +974,6 @@ TODO
 * cosocket: add configure options for different strategies of handling the cosocket connection exceeding in the pools.
 * review and apply vadim-pavlov's patch for [ngx.location.capture](#ngxlocationcapture)'s `extra_headers` option
 * use `ngx_hash_t` to optimize the built-in header look-up process for [ngx.req.set_header](#ngxreqset_header), [ngx.header.HEADER](#ngxheaderheader), and etc.
-* add directives to run Lua codes when Nginx stops.
 * add `ignore_resp_headers`, `ignore_resp_body`, and `ignore_resp` options to [ngx.location.capture](#ngxlocationcapture) and [ngx.location.capture_multi](#ngxlocationcapture_multi) methods, to allow micro performance tuning on the user side.
 * add automatic Lua code time slicing support by yielding and resuming the Lua VM actively via Lua's debug hooks.
 * add `stat` mode similar to [mod_lua](https://httpd.apache.org/docs/trunk/mod/mod_lua.html).

doc/HttpLuaModule.wiki

@@ -809,7 +809,6 @@ phases.
 * cosocket: add configure options for different strategies of handling the cosocket connection exceeding in the pools.
 * review and apply vadim-pavlov's patch for [[#ngx.location.capture|ngx.location.capture]]'s <code>extra_headers</code> option
 * use <code>ngx_hash_t</code> to optimize the built-in header look-up process for [[#ngx.req.set_header|ngx.req.set_header]], [[#ngx.header.HEADER|ngx.header.HEADER]], and etc.
-* add directives to run Lua codes when Nginx stops.
 * add <code>ignore_resp_headers</code>, <code>ignore_resp_body</code>, and <code>ignore_resp</code> options to [[#ngx.location.capture|ngx.location.capture]] and [[#ngx.location.capture_multi|ngx.location.capture_multi]] methods, to allow micro performance tuning on the user side.
 * add automatic Lua code time slicing support by yielding and resuming the Lua VM actively via Lua's debug hooks.
 * add <code>stat</code> mode similar to [https://httpd.apache.org/docs/trunk/mod/mod_lua.html mod_lua].
@@ -1607,8 +1606,8 @@ Note that this handler always runs ''after'' the standard [[HttpRewriteModule]].
     location /foo {
         set $a 12; # create and initialize $a
         set $b ""; # create and initialize $b
-        rewrite_by_lua_block { 
-            ngx.var.b = tonumber(ngx.var.a) + 1 
+        rewrite_by_lua_block {
+            ngx.var.b = tonumber(ngx.var.a) + 1
         }
         echo "res = $b";
     }
@@ -1622,8 +1621,8 @@ On the other hand, the following will not work as expected:
     ?  location /foo {
     ?      set $a 12; # create and initialize $a
     ?      set $b ''; # create and initialize $b
-    ?      rewrite_by_lua_block { 
-    ?          ngx.var.b = tonumber(ngx.var.a) + 1 
+    ?      rewrite_by_lua_block {
+    ?          ngx.var.b = tonumber(ngx.var.a) + 1
     ?      }
     ?      if ($b = '13') {
     ?         rewrite ^ /bar redirect;
@@ -1698,8 +1697,8 @@ If the [[HttpRewriteModule]]'s [[HttpRewriteModule#rewrite|rewrite]] directive i
 <geshi lang="nginx">
     location /foo {
         rewrite ^ /bar;
-        rewrite_by_lua_block { 
-            ngx.exit(503) 
+        rewrite_by_lua_block {
+            ngx.exit(503)
         }
     }
     location /bar {
@@ -1892,8 +1891,8 @@ Here is an example of overriding a response header (or adding one if absent) in
 <geshi lang="nginx">
     location / {
         proxy_pass http://mybackend;
-        header_filter_by_lua_block { 
-            ngx.header.Foo = "blah" 
+        header_filter_by_lua_block {
+            ngx.header.Foo = "blah"
         }
     }
 </geshi>
@@ -1964,8 +1963,8 @@ The Lua code can pass its own modified version of the input data chunk to the do
 <geshi lang="nginx">
     location / {
         proxy_pass http://mybackend;
-        body_filter_by_lua_block { 
-            ngx.arg[1] = string.upper(ngx.arg[1]) 
+        body_filter_by_lua_block {
+            ngx.arg[1] = string.upper(ngx.arg[1])
         }
     }
 </geshi>
@@ -2006,11 +2005,11 @@ When the Lua code may change the length of the response body, then it is require
     location /foo {
         # fastcgi_pass/proxy_pass/...
 
-        header_filter_by_lua_block { 
-            ngx.header.content_length = nil 
+        header_filter_by_lua_block {
+            ngx.header.content_length = nil
         }
-        body_filter_by_lua_block { 
-            ngx.arg[1] = string.len(ngx.arg[1]) .. "\n" 
+        body_filter_by_lua_block {
+            ngx.arg[1] = string.len(ngx.arg[1]) .. "\n"
         }
     }
 </geshi>
@@ -3688,8 +3687,8 @@ Lua tables can be used for both requests and responses when the number of subreq
     table.insert(reqs, { "/memcached" })
 
     -- issue all the requests at once and wait until they all return
-    local resps = { 
-        ngx.location.capture_multi(reqs) 
+    local resps = {
+        ngx.location.capture_multi(reqs)
     }
 
     -- loop over the responses table
@@ -5201,8 +5200,8 @@ For example,
 
 <geshi lang="nginx">
     location = /md5 {
-        content_by_lua_block { 
-            ngx.say(ngx.md5("hello")) 
+        content_by_lua_block {
+            ngx.say(ngx.md5("hello"))
         }
     }
 </geshi>