This module adds responses of other locations before and after the current location's response.
It is implemented as an output filter, the contents of the main request and subrequests to other locations are not buffered completely and are still sent to the client in a streaming fashion. Because the length of the final response body is unkown while sending the HTTP headers, the HTTP chunked encoding is always used here.
By default the module is not built, it is necessary to enable its build with
./configure --with-http_addition_module at compilation time.
Example:
location / {
add_before_body /before_action;
add_after_body /after_action;
} Note that as of 0.8.17 no contents will be added if the current location is served as a subrequest itself. Consider the following example:
location /foo {
add_before_body /bar;
}
location /bar {
add_before_body /baz;
} Then accessing /foo won't get /baz inserted before the contents of the subrequest /bar.
Also note that at this time, only strings can be used in before/after body locations, not variables. So
location / {
set $before_action /before_action;
add_before_body $before_action;
} will not work as expected (although the configuration file will still load properly).
syntax:*add_before_body uri*
default:*no*
context:*http, server, location*
Directive adds content of uri before the response body, issued as a result of the work of the assigned subrequest.
syntax:*add_after_body uri*
default:*no*
context:*http, server, location*
Directive adds content of uri after the response body, issued as a result of the work of the assigned subrequest.
syntax:*addition_types mime-type [mime-type ...]*
default:*text/html*
context:*http, server, location*
Directive (since 0.7.9) allows you to add text only to locations of the specified MIME-types (defaults to "text/html").
(Before 0.8.17, this directive was mispelled as "addtion_types" in the source. This bug has been fixed in 0.8.17.)