Keep the response body in memory

zimmerle · zimmerle · commit 221a134181cf · 2016-03-17T13:59:57.000-03:00
This commit fix the issue #8. This patch needs to be polished, it is only necessary if the SecResponseBody is enabled.
diff --git a/src/ngx_http_modsecurity_header_filter.c b/src/ngx_http_modsecurity_header_filter.c
@@ -370,6 +370,13 @@ ngx_int_t ngx_http_modsecurity_header_filter(ngx_http_request_t *r)
         return ngx_http_next_header_filter(r);
     }
 
+    /**
+     * Lets ask nginx to keep the response body in memory
+     *
+     * FIXME: I don't see a reason to keep it `1' when SecResponseBody is disabled.
+     */
+    r->filter_need_in_memory = 1;
+
     ctx->processed = 1;
     /*
      *

Original file line number	Diff line number	Diff line change
`@@ -370,6 +370,13 @@ ngx_int_t ngx_http_modsecurity_header_filter(ngx_http_request_t *r)`
`370`	`370`	`return ngx_http_next_header_filter(r);`
`371`	`371`	`}`
`372`	`372`
	`373`	`+ /**`
	`374`	`+ * Lets ask nginx to keep the response body in memory`
	`375`	`+ *`
	`376`	+ * FIXME: I don't see a reason to keep it `1' when SecResponseBody is disabled.
	`377`	`+ */`
	`378`	`+ r->filter_need_in_memory = 1;`
	`379`	`+`
`373`	`380`	`ctx->processed = 1;`
`374`	`381`	`/*`
`375`	`382`	`*`