Message from discussion end event missed in client http response
Received: by 10.101.182.28 with SMTP id j28mr2415732anp.29.1309104549050;
Sun, 26 Jun 2011 09:09:09 -0700 (PDT)
Received: by 10.90.58.22 with SMTP id g22ls1216036aga.2.gmail; Sun, 26 Jun
2011 09:08:54 -0700 (PDT)
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
Date: Sun, 26 Jun 2011 09:08:54 -0700 (PDT)
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0)
Subject: Re: end event missed in client http response
From: Bruno Jouhier <bjouh...@gmail.com>
To: nodejs <firstname.lastname@example.org>
Content-Type: text/plain; charset=ISO-8859-1
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.
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.
> 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
> 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