Skip to content

Commit 41e1e6e

Browse files
sam-githubItalo A. Casas
authored andcommitted
tls: do not refer to secureOptions as flags
Its confusing to have multiple names for the same thing, use secureOptions consistently. PR-URL: #9800 Reviewed-By: Roman Reiss <me@silverwind.io> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
1 parent 7c3d280 commit 41e1e6e

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

‎lib/_tls_common.js‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,9 +12,9 @@ var crypto = null;
1212
constbinding=process.binding('crypto');
1313
constNativeSecureContext=binding.SecureContext;
1414

15-
functionSecureContext(secureProtocol,flags,context){
15+
functionSecureContext(secureProtocol,secureOptions,context){
1616
if(!(thisinstanceofSecureContext)){
17-
returnnewSecureContext(secureProtocol,flags,context);
17+
returnnewSecureContext(secureProtocol,secureOptions,context);
1818
}
1919

2020
if(context){
@@ -29,7 +29,7 @@ function SecureContext(secureProtocol, flags, context) {
2929
}
3030
}
3131

32-
if(flags)this.context.setOptions(flags);
32+
if(secureOptions)this.context.setOptions(secureOptions);
3333
}
3434

3535
exports.SecureContext=SecureContext;

0 commit comments

Comments
 (0)