stub_status always give me 0 Reading when upgraded to 1.4.1
Tsz Ming WONG
tszming at gmail.com
Wed Jul 17 14:30:30 UTC 2013
Thank you (and Maxim) for the detail explanation!
On Wed, Jul 17, 2013 at 7:21 PM, Ruslan Ermilov <ru at nginx.com> wrote:
> On Wed, Jul 17, 2013 at 06:48:53PM +0800, Tsz Ming WONG wrote:
> > Hi,
> > On Wed, Jul 17, 2013 at 6:29 PM, Maxim Dounin <mdounin at mdounin.ru>
> > wrote:
> > stub_status
> > Thanks for the explanation.
> > But given that this is a busy server, sound abnormal if it always
> return a
> > 0? (according to the doc: reading - nginx reads request header)
> It means that your clients and nginx are fast enough, enjoy. If you
> absolutely need it to become non-zero, you can emulate a slow client
> like this:
> ( echo 'GET / HTTP/1.0' ; sleep 42 ; echo ) | nc 127.0.0.1 80
> substituting the address and port of your server. During these 42
> seconds, the status will show at least one connection in the
> "reading" state.
> nginx mailing list
> nginx at nginx.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx