499 error in nginx

Seun Osewa seun.osewa at gmail.com
Mon Aug 27 15:08:00 MSD 2007


Example.com??

On 8/27/07, Abhishek Singh <opensourcelearning at gmail.com> wrote:
>
> Hi Igor,
>
> 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.
>
> Thanks alot Igor
>
>
>
> On 8/27/07, Igor Sysoev <is at rambler-co.ru> wrote:
> >
> > On Mon, Aug 27, 2007 at 04:01:33PM +0530, Abhishek Singh wrote:
> >
> > > I am using nginx as a web and proxy server for mongrel, its working
> > fine but
> > > i am facing one problem with nginx , i am getting 499 http client
> > error code
> > > in nginx log file, earlier when i was using lighttpd and pound so i
> > was not
> > > getting 499 error. So can anyone please explain me what is the main
> > problem
> > > and how can i resolve this and what is the exact definition of 499
> > http
> > > status code.
> >
> > src/http/ngx_http_request.h:
> >
> > /*
> > * HTTP does not define the code for the case when a client closed
> > * the connection while we are processing its request so we introduce
> > * own code to log such situation when a client has closed the connection
> >
> > * before we even try to send the HTTP header to it
> > */
> > #define NGX_HTTP_CLIENT_CLOSED_REQUEST     499
> >
> >
> > --
> > Igor Sysoev
> > http://sysoev.ru/en/
> >
> >
>


-- 
Seun Osewa
http://www.nairaland.com [vast Nigerian forum]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20070827/96b2841f/attachment.html>


More information about the nginx mailing list