Skip to content

Commit

Permalink
tls: do not refer to secureOptions as flags
Browse files Browse the repository at this point in the history
Its confusing to have multiple names for the same thing, use
secureOptions consistently.

PR-URL: nodejs#9800
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
  • Loading branch information
sam-github committed Dec 12, 2016
1 parent 475b8db commit a28e949
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions lib/_tls_common.js
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,9 @@ var crypto = null;
const binding = process.binding('crypto');
const NativeSecureContext = binding.SecureContext;

function SecureContext(secureProtocol, flags, context) {
function SecureContext(secureProtocol, secureOptions, context) {
if (!(this instanceof SecureContext)) {
return new SecureContext(secureProtocol, flags, context);
return new SecureContext(secureProtocol, secureOptions, context);
}

if (context) {
Expand All @@ -29,7 +29,7 @@ function SecureContext(secureProtocol, flags, context) {
}
}

if (flags) this.context.setOptions(flags);
if (secureOptions) this.context.setOptions(secureOptions);
}

exports.SecureContext = SecureContext;
Expand Down

0 comments on commit a28e949

Please sign in to comment.