API question: large data processing handler
mdounin at mdounin.ru
Sun Jul 7 21:54:38 UTC 2013
On Sun, Jul 07, 2013 at 03:22:56AM -0600, Julien Zefi wrote:
> > >
> > > > Haven't looked any further.
> > > >
> > >
> > > thanks for your comments. Taking in count tha changes provided i still
> > face
> > > this problem:
> > >
> > > #0 0x00000000004065d6 in ngx_palloc (pool=0x0, size=16) at
> > > src/core/ngx_palloc.c:122
> > > #1 0x0000000000406a73 in ngx_pcalloc (pool=0x0, size=16) at
> > > src/core/ngx_palloc.c:305
> > > #2 0x000000000046b76d in ngx_http_chunked_header_filter (r=0x6eebb0)
> > > at src/http/modules/ngx_http_chunked_filter_module.c:82
> > > #3 0x000000000046bdc4 in ngx_http_range_header_filter (r=0x6eebb0)
> > > at src/http/modules/ngx_http_range_filter_module.c:160
> > >
> > > why my pool is always NULL ? do i am missing some initialization
> > somewhere ?
> > Part of the backtrace shown suggests you trigger request activity after
> > the request was freed. Most likely you've forgot r->main->count++.
> thanks, that helped for the next calls.
> When i receive a client in HTTP/1.1, my binary data is not being send with
> the transfer chunked encoding headers, i refer to the header and footer to
> each chunk of content, the HTTP header is set properly, so i would like to
> know if i need to do something to enable the chunked header/footer or is
> this is automatic ?, also.. whats the most probable thing that could mess
> up that feature when developing a plugin ?
Chunked transfer encoding is enabled automatically as long as it's
supported by a client and there is no content length. Try looking
into src/http/modules/ngx_http_chunked_filter_module.c for more
More information about the nginx-devel