Martin, I believe you meant secureProtocol instead of secureOptions?
The issue still persists with these options.
On Friday, February 14, 2014 6:40:02 PM UTC+1, Martin Gonzalez wrote:
>
> I think this might be related to a bug in openssl implementation.
>
> Try adding this options to the request:
Hey Fedor.
The `connect` event is never fired on the https server instance. However,
the client does send a CONNECT header.
On Friday, February 14, 2014 6:46:06 PM UTC+1, Fedor Indutny wrote:
>
> Heya!
>
> Check out `connect` event:
> http://nodejs.org/api/http.html#http_event_connect
>
> On
Heya!
Check out `connect` event: http://nodejs.org/api/http.html#http_event_connect
On Fri, Feb 14, 2014 at 9:40 PM, Martin Gonzalez wrote:
> I think this might be related to a bug in openssl implementation.
>
> Try adding this options to the request:
>
> options.secureOptions = require('c
I think this might be related to a bug in openssl implementation.
Try adding this options to the request:
options.secureOptions = require('constants').SSL_OP_NO_TLSv1_2;
options.ciphers =
'ECDHE-RSA-AES256-SHA:AES256-SHA:RC4-SHA:RC4:HIGH:!MD5:!aNULL:!EDH:!AESGCM';
options.honorC
I'm trying to create a HTTPS proxy server in Node.JS v0.10.24 using a
self-signed certificate. Here's the code I'm using:
var https = require('https');
var server = https.createServer({
key: fs.readFileSync('key.pem'),
cert: fs.readFileSync('cert.pem')
});
server.on('request', functio
