Thanks Ben!
I'd assume that something like this in the requestListener is the best way
to set the timeouts in the interim:
function requestTimeout() {
request.abort();
}
function responseTimeout() {
errorResponse(500, 'TIMEOUT');
}
request.setTimeout(30000, requestTimeout);
response.setTimeout(30000, responseTimeout);
-ch
On Wednesday, April 24, 2013 12:04:03 PM UTC-7, Ben Noordhuis wrote:
>
> On Wed, Apr 24, 2013 at 8:46 PM, Craig Hockenberry
> <[email protected] <javascript:>> wrote:
> > I'd like to change the socket timeout for an HTTPS server instance, but
> find
> > that the following doesn't work:
> >
> > var options = {
> > key: fs.readFileSync('ssl/my.key'),
> > cert: fs.readFileSync('ssl/my.crt'),
> > ca: fs.readFileSync('ssl/myca.crt'),
> > handshakeTimeout: 20000,
> > };
> > var server = https.createServer(options, requestListener);
> > server.setTimeout(30000);
> > server.listen(8080);
> >
> > In our development environment, where we use an HTTP server, the timeout
> > works great.
> >
> > I'm wondering if there is some technical reason why SSL connections
> can't
> > time out, or if this is just an oversight.
> >
> > Thanks in advance for any help/insight.
> >
> > -ch
>
> It's an oversight. I've filed an issue[1].
>
> [1] https://github.com/joyent/node/issues/5361
>
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
