[Q]: Why nginx stop feeding content to a custom filter module after processing 64K of data?
mdounin at mdounin.ru
Tue Feb 7 13:14:45 UTC 2017
On Mon, Feb 06, 2017 at 08:16:56PM +0300, Andrey Kulikov wrote:
> > (Note well that your filter misuses NGX_HTTP_SUB_BUFFERED flag.
> > This will cause undefined behaviour if the filter is used with the
> > sub filter.)
> Is there are more elegant solution to achieve desired functionality?
> Without patching nginx sources by adding new NGX_HTTP_*_BUFFERED constant?
> There is only limited number of slots available, and if not with sub
> filter, it may cause incompatibility with
> other external modules, if they happens to use the same bit.
AFAIK, there is no good solution.
More information about the nginx-devel