Hello!
On Thu, Oct 17, 2019 at 04:42:54PM -0400, Ansuel wrote:
> I don't know if this is a bug or not but... yes you were right...
>
> All the work should be done in the ngx_http_read_client_request_body
> handler, as it does duplicate the r connection to another address
>
> What confused me is
I don't know if this is a bug or not but... yes you were right...
All the work should be done in the ngx_http_read_client_request_body
handler, as it does duplicate the r connection to another address
What confused me is the fact that this is only done in http2 connections...
I really don't know
Hello!
On Mon, Oct 14, 2019 at 02:41:33PM -0400, Ansuel wrote:
> this is what i have in the module handler function
>
> rc = ngx_http_read_client_request_body(r, ngx_http_test_read_req);
> if (rc != NGX_OK && rc != NGX_AGAIN) {
> return rc;
> }
this is what i have in the module handler function
rc = ngx_http_read_client_request_body(r, ngx_http_test_read_req);
if (rc != NGX_OK && rc != NGX_AGAIN) {
return rc;
}
And this is what i have in
ngx_http_test_read_req
char *buffer = n
Hello!
On Sun, Oct 13, 2019 at 08:47:16PM -0400, Ansuel wrote:
> Hello, i'm developing a custom module that needs to read the request body to
> get some data from it.
> To read the request body i'm using
>
> ngx_http_read_client_request_body
>
> and in the callback i use
>
> for (in = r->r
Hello, i'm developing a custom module that needs to read the request body to
get some data from it.
To read the request body i'm using
ngx_http_read_client_request_body
and in the callback i use
for (in = r->request_body->bufs; in; in = in->next) {
len = ngx_buf_size(
