Received: by 10.101.182.28 with SMTP id j28mr2415732anp.29.1309104549050;
        Sun, 26 Jun 2011 09:09:09 -0700 (PDT)
X-BeenThere: nodejs@googlegroups.com
Received: by 10.90.58.22 with SMTP id g22ls1216036aga.2.gmail; Sun, 26 Jun
 2011 09:08:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.90.9.11 with SMTP id 11mr550033agi.26.1309104534457; Sun, 26
 Jun 2011 09:08:54 -0700 (PDT)
Received: by a11g2000yqm.googlegroups.com with HTTP; Sun, 26 Jun 2011 09:08:54
 -0700 (PDT)
Date: Sun, 26 Jun 2011 09:08:54 -0700 (PDT)
In-Reply-To: <3aee7523-eadd-483f-830a-c7d3a925650f@w4g2000yqm.googlegroups.com>
References: <3aee7523-eadd-483f-830a-c7d3a925650f@w4g2000yqm.googlegroups.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0)
 Gecko/20100101 Firefox/5.0,gzip(gfe)
Message-ID: <063a800d-2b03-48fc-8918-ba20d308f10d@a11g2000yqm.googlegroups.com>
Subject: Re: end event missed in client http response
From: Bruno Jouhier <bjouh...@gmail.com>
To: nodejs <nodejs@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

You should also trap the "error" event. If an error occurs, you will
get an error event, but you won't get any end event.

Bruno

On Jun 26, 2:06=A0pm, Kris Walker <kixxa...@gmail.com> wrote:
> While investigating another HTTP problem I discovered that there are
> times when the 'end' event is sometimes never emitted on an HTTP
> client response object.
>
> You can run this test script like Curl, by passing in a single
> argument; the full HTTP URL of your target.
>
> https://gist.github.com/1047559
>
> For example:
>
> If I call `node test_request.jshttp://www.example.com`or `node
> test_request.jshttp://www.amazon.com`I always see the 'end' event
> fired.
>
> But, sometimes, when I do `node test_request.jshttp://www.google.com`
> the 'end' event is sometimes never called, but not always.
>
> Any ideas on why this is? Is it expected? And if so, what are some