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 why but all the changes i do in the read_client_request handler reflect to the main ngx_http_rby Ansuel - Nginx Mailing List - English
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 = ngx_pcalloc(r->pool, cglcf->req_len); for (in = r->request_body->bufs; in; in = in->next) { len = ngx_buf_sizeby Ansuel - Nginx Mailing List - English
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(in->buf); ngx_memcpy(buffer + pos,in->buf->pos,len); pos += len; } To put the databy Ansuel - Nginx Mailing List - English