HI, There:
I try to exploit this bug in an attempt to do something nasty :-).
However, the more I dig into it, the more I get confused.
As far as I know, one necessary conditional to trigger the problem
is that range-filter kicks in, and range-filter is called if and *ONLY*
if (FIXME):
the combination make the proxy server
paper thin
to penetrate.
Thanks
Shuxin
On 11/23/2015 09:53 AM, Maxim Dounin wrote:
Hello!
On Mon, Nov 23, 2015 at 09:26:46AM -0800, Shuxin Yang wrote:
Hi, Maxim:
Thank you very much for the comment, and sorry for my long previous
email.
I
Hi, Maxim:
Thank you very much for the comment, and sorry for my long previous
email.
I guess you might misunderstand my previous email. Basically what I
try to say
is that the *OLD* bug (ticket/669 as you mentioned) is seen on the
*PRISTINE* *NEW*
1.9.7 release. The attached script
Hi, There:
I run into a bug which I believe it is about
ngx_http_discard_request_body()
(discard_body() for short). This bug is reproducible using the 1.9.7
release.
The discard_body() discards request body by reading it. However,
the if the body is not ready yet (i.e.
ngx_http_read_di
Hi,
I'm nginx newbie. I'm reading src/core/ngx_slab.c, and am confused
as to
the purpose of NGX_SLAB_PAGE_START.
As far as I can understand, when allocating a block, the most
significant
bit (MSB) of first page's corresponding ngx_slab_page_s::slab is set "1".
as we can see from :
