499 error in nginx

Abhishek Singh opensourcelearning at gmail.com
Tue Aug 28 15:15:53 MSD 2007


On 8/28/07, Abhishek Singh <opensourcelearning at gmail.com> wrote:
>
>
>
> On 8/28/07, Igor Sysoev <is at rambler-co.ru> wrote:
> >
> > On Tue, Aug 28, 2007 at 02:32:46PM +0530, Abhishek Singh wrote:
> >
> > > On 8/27/07, Abhishek Singh <opensourcelearning at gmail.com> wrote:
> > > >
> > > > On 8/27/07, Igor Sysoev < is at rambler-co.ru> wrote:
> > > > >
> > > > > On Mon, Aug 27, 2007 at 04:30:59PM +0530, Abhishek Singh wrote:
> > > > >
> > > > > > thanks for replying so fast , i am using nginx as a proxy for
> > mongrel
> > > > > , so
> > > > > > in this scenario my nginx will be client or browser (who has
> > sent this
> > > > >
> > > > > > request) because i am using alertra for website monitoring by
> > urls so
> > > > > there
> > > > > > is one url where i am getting error and alertra is showing
> > > > > >
> > > > > > Time: 08/27/2007 04:03:09 US/Eastern
> > > > > >  Abbreviation: slidview
> > > > > >  URL: http://www.example.com/inet/scalable-web-a
> > > > > >  Checked From: Atlanta USA
> > > > > >  Result: Error
> > > > > >  Result Message: Connection to HTTP service failed
> > > > > >  Server Code: None
> > > > > >  Server Message: Unrecognized HTTP error
> > > > > >  File Size: N/A
> > > > > >  Elapsed Time: 30.07 Seconds
> > > > > >
> > > > > > when i am checking in nginx log so for the same url i am getting
> > 499
> > > > > from
> > > > > > www.alertra.com
> > > > > >
> > > > > > as per source file definition "when a client closed
> > > > > > * the connection while we are processing its request" then nginx
> > will
> > > > > log
> > > > > > 499 in log file so why alertra will close the connection. or it
> > can
> > > > > happen
> > > > > > timeout setting in alertra, there is timeout setting  of 30
> > second for
> > > > > that
> > > > > > url. Igor can u please explain me this.
> > > > >
> > > > > I think, the request goes to mongrel and it does not response for
> > > > > 30 seconds. The client closes connection after its timeout.
> > > > >
> > > > > Thanks allot Igor , i was also thinking same thing .
> > > > I really appreciate ur fast reponse.
> > > > Keep it up buddy.
> > >
> > > Should i worry about 499 error , is this serious issue for a popular
> > web
> > > site . Please share your views on this. Waiting for your response .
> >
> > You may log $request_time. If you see 499 with long $request_time it
> > means in general that client does not wait your server.
> >
> >
> > --
> > Igor Sysoev
> > http://sysoev.ru/en/
>
>
> Hi Igor,
>
> If you see 499 with long $request_time it means in general that client
> does not wait your server. Can u tell me exactly what it means .
>
>
> Igor
>


$request_time is client request time or nginx request time for backend
> mongrel.
>

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20070828/e48ab897/attachment.html>


More information about the nginx mailing list