Quick correction: its the underlying node https.request object that has changed the default for rejectUnauthorized from false to true between node 0.8 to node 0.10, so TJ's superagent is exhibiting the same behavior. It appears to be by design. Even it it breaks some things, I think the new default is correct.
-g On Thursday, April 11, 2013 1:21:34 PM UTC-7, George Snelling wrote: > > We have a node server that always serves https, even in dev and test mode. > In dev and test we use self-signed certs. Our test harness uses Mikeal's > request module, and our tests failed with DEPTH_ZERO_SELF_SIGNED_CERT > running against node v0.10. It appears that against node v0.8.x the current > version of request defaults strictSSL to false, meaning that it will > connect with a self-signed certificate. Against node v0.10.x, however, it > appears that the default for that option is now true. I'm not sure if this > is a bug, or by design, but it is not reflected in the request readme: > https://github.com/mikeal/request#requestoptions-callback. There were > several open bugs and pull requests in various projects on similar topics, > so I thought I'd post it here. Setting strictSSL explicitly to false when > creating the request got us working. > > -George > -- -- 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.
