doc: add the description for precontent_by_lua_no_postpone

Author: HanadaLee

README.markdown

@@ -1198,6 +1198,7 @@ Directives
 * [lua_http10_buffering](#lua_http10_buffering)
 * [rewrite_by_lua_no_postpone](#rewrite_by_lua_no_postpone)
 * [access_by_lua_no_postpone](#access_by_lua_no_postpone)
+* [precontent_by_lua_no_postpone](#precontent_by_lua_no_postpone)
 * [lua_transform_underscores_in_response_headers](#lua_transform_underscores_in_response_headers)
 * [lua_check_client_abort](#lua_check_client_abort)
 * [lua_max_pending_timers](#lua_max_pending_timers)
@@ -1878,6 +1879,9 @@ That is, if a request for /images/foo.jpg comes in and the file does not exist,
 
 You can use [precontent_by_lua_block](#precontent_by_lua_block) to perform some preparatory functions after the access phase handler but before the proxy or other content handler. Especially some functions that cannot be performed in [balancer_by_lua_block](#balancer_by_lua_block).
 
+you can use the [precontent_by_lua_no_postpone](#precontent_by_lua_no_postpone) directive to control when to run this handler inside the "precontent" request-processing phase
+of Nginx.
+
 [Back to TOC](#directives)
 
 precontent_by_lua_file
@@ -3710,6 +3714,19 @@ This directive was first introduced in the `v0.9.20` release.
 
 [Back to TOC](#directives)
 
+precontent_by_lua_no_postpone
+-------------------------
+
+**syntax:** *precontent_by_lua_no_postpone on|off*
+
+**default:** *precontent_by_lua_no_postpone off*
+
+**context:** *http*
+
+Controls whether or not to disable postponing [precontent_by_lua*](#precontent_by_lua_block) directives to run at the end of the `precontent` request-processing phase. By default, this directive is turned off and the Lua code is postponed to run at the end of the `precontent` phase.
+
+[Back to TOC](#directives)
+
 lua_transform_underscores_in_response_headers
 ---------------------------------------------
 

doc/HttpLuaModule.wiki

@@ -1524,6 +1524,8 @@ That is, if a request for /images/foo.jpg comes in and the file does not exist,
 
 You can use [[#precontent_by_lua_block|precontent_by_lua_block]] to perform some preparatory functions after the access phase handler but before the proxy or other content handler. Especially some functions that cannot be performed in [[#balancer_by_lua_block|balancer_by_lua_block]].
 
+You can use the [[#precontent_by_lua_no_postpone|precontent_by_lua_no_postpone]] directive to control when to run this handler inside the "precontent" request-processing phase of Nginx.
+
 == precontent_by_lua_file ==
 
 '''syntax:''' ''precontent_by_lua_file <path-to-lua-script-file>''
@@ -3070,6 +3072,16 @@ Controls whether or not to disable postponing [[#access_by_lua|access_by_lua*]]
 
 This directive was first introduced in the <code>v0.9.20</code> release.
 
+== precontent_by_lua_no_postpone ==
+
+'''syntax:''' ''precontent_by_lua_no_postpone on|off''
+
+'''default:''' ''precontent_by_lua_no_postpone off''
+
+'''context:''' ''http''
+
+Controls whether or not to disable postponing [[#precontent_by_lua_block|precontent_by_lua_block*]] directives to run at the end of the <code>precontent</code> request-processing phase. By default, this directive is turned off and the Lua code is postponed to run at the end of the <code>precontent</code> phase.
+
 == lua_transform_underscores_in_response_headers ==
 
 '''syntax:''' ''lua_transform_underscores_in_response_headers on|off''