From 41e1e6eb35a7623546d8fc4f9345436710e7da9e Mon Sep 17 00:00:00 2001
From: Sam Roberts <vieuxtech@gmail.com>
Date: Tue, 22 Nov 2016 13:23:06 -0800
Subject: [PATCH] tls: do not refer to secureOptions as flags

Its confusing to have multiple names for the same thing, use
secureOptions consistently.

PR-URL: https://github.com/nodejs/node/pull/9800
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
---
 lib/_tls_common.js | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lib/_tls_common.js b/lib/_tls_common.js
index 6e98c1ee4d66d2..9cb70453860484 100644
--- a/lib/_tls_common.js
+++ b/lib/_tls_common.js
@@ -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) {
@@ -29,7 +29,7 @@ function SecureContext(secureProtocol, flags, context) {
     }
   }
 
-  if (flags) this.context.setOptions(flags);
+  if (secureOptions) this.context.setOptions(secureOptions);
 }
 
 exports.SecureContext = SecureContext;