-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https: make opts optional & immutable when create #13599
https: make opts optional & immutable when create #13599
Conversation
`opts` in `createServer` will be immutable that won't change origional opts value. What's more, it's optional which can make `requestListener` be the first argument. Refs: nodejs#13584
@@ -46,7 +46,7 @@ added: v8.0.0 | |||
|
|||
See [`http.Server#keepAliveTimeout`][]. | |||
|
|||
## https.createServer(options[, requestListener]) | |||
## https.createServer([options][, requestListener]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we have to change this in the documentation, since Huh... I take that back, it doesn't seem to enforce a minimum configuration...tls.Server()
will still require a configuration (a certificate and key at minimum). The benefit of guarding early before tls.Server()
is called is to avoid strange JavaScript runtime errors.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But a test in either way should be added.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@refack the test is in test/parallel/test-https-immutable-options.js, which tested in server2
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need a test like
// validate that `createServer` can work with no arguments
const server2 = https.createServer();
assert.ok(server2);
assert.strictEqual(server1.NPNProtocols.compare(dftProtocol.NPNProtocols), 0);
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@refack done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1 style nit
1 request for test (assert signature)
lib/https.js
Outdated
requestListener = opts; | ||
opts = undefined; | ||
} | ||
opts = opts ? util._extend({}, opts) : {}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you can use Object.assign
(and give opts
a default in L34)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@refack Did you benchmark that util._extend
is faster than Object.assign
by now? Last I heard it was not, which is why we still use util._extend
for most internals.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@addaleax I was about to say that but I'm not sure it matters in the case of starting a server. *shrug*
util._extend()
does have significantly more usage in core though according to a quick grep.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmmm, so I'm waiting for a result.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMHO this is a "cold spot" so I opt for standard 🤷♂️
Any way this could be simply
opts = util._extend({}, opts);
@XadillaX I think you're free to decide
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
> console.time('assign');for(var i=0; i < 1E7; ++i) { Object.assign({1:1, 2:2, 3:3}, {a:1, b:2, c:3}); };console.timeEnd('assign')
assign: 9825.217ms
undefined
> console.time('_extend');for(var i=0; i < 1E7; ++i) { u._extend({1:1, 2:2, 3:3}, {a:1, b:2, c:3}); };console.timeEnd('_extend')
_extend: 6174.819ms
undefined
so util._extend
is ~ 60% of Object.assign
.
IMHO if it's not better than 50%, Object.assign
should be prefered
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If util._extend
uses more than Object.assign
, I think I can change it back to util._extend
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@refack, And if necessary, I think we can open a new PR about changing all util._extend
to Object.assign
in this file next time. Because it not only contains one util._extend
here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@refack, And if necessary, I think we can open a new PR about changing all util._extend to Object.assign in this file next time. Because it not only contains one util._extend here.
We can do this when V8
optimizes Object.assign
to be <= util._extend
...
@@ -46,7 +46,7 @@ added: v8.0.0 | |||
|
|||
See [`http.Server#keepAliveTimeout`][]. | |||
|
|||
## https.createServer(options[, requestListener]) | |||
## https.createServer([options][, requestListener]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But a test in either way should be added.
35b1e77
to
26d4efb
Compare
assert.deepStrictEqual(opts, { foo: 'bar' }); | ||
assert.strictEqual(server1.NPNProtocols.compare(dftProtocol.NPNProtocols), 0); | ||
|
||
const mustNotCall = common.mustNotCall('dummy callback'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be best to just omit the argument here, since if the function is called for some odd reason the default message should be slightly more descriptive and good enough.
const server1 = https.createServer(opts); | ||
|
||
assert.deepStrictEqual(opts, { foo: 'bar' }); | ||
assert.strictEqual(server1.NPNProtocols.compare(dftProtocol.NPNProtocols), 0); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it should suffice to just compare the NPNProtocols
references. That way we know for sure that our options weren't overridden:
assert.strictEqual(server1.NPNProtocols, dftProtocol.NPNProtocols);
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mscdex I think we can't, because NPNProtocols
hasn't been cached yet. 2 calls to tls.convertNPNProtocols
won't return the same reference.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah ok I see it now. Perhaps we should at least choose a different set of protocols then, so as to differentiate from the default NPN protocols (perhaps just use one protocol?).
@@ -46,7 +46,7 @@ added: v8.0.0 | |||
|
|||
See [`http.Server#keepAliveTimeout`][]. | |||
|
|||
## https.createServer(options[, requestListener]) | |||
## https.createServer([options][, requestListener]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need a test like
// validate that `createServer` can work with no arguments
const server2 = https.createServer();
assert.ok(server2);
assert.strictEqual(server1.NPNProtocols.compare(dftProtocol.NPNProtocols), 0);
lib/https.js
Outdated
requestListener = opts; | ||
opts = undefined; | ||
} | ||
opts = opts ? Object.assign({}, opts) : {}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you can change this to
opts = Object.assign({}, opts);
const server2 = https.createServer(mustNotCall); | ||
|
||
assert.strictEqual(server2.NPNProtocols.compare(dftProtocol.NPNProtocols), 0); | ||
assert.strictEqual(mustNotCall, server2._events.request); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we replace this with
assert.strictEqual(server2.listeners('request'), 1);
assert.strictEqual(server2.listeners('request')[0], mustNotCall);
assert.strictEqual(server1.NPNProtocols.compare(dftProtocol.NPNProtocols), 0); | ||
|
||
const mustNotCall = common.mustNotCall(); | ||
const server2 = https.createServer(mustNotCall); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The comment below doesn't match the behavior of this line. If we're testing no arguments, it should just be https.createServer()
.
Otherwise we could add a separate test below for no arguments.
|
||
// validate that `createServer` can work with no arguments | ||
tls.convertNPNProtocols([ 'http/1.1', 'http/1.0' ], dftProtocol); | ||
assert.ok(server2); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: It doesn't harm but I think this is redundant. An error would be thrown below if server2
is falsy.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@refack, Shall I?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a style we now use more often (helps frame every test case), but IMHO it's up to you... that was for the other comment
I'm 👍 for keeping it, but maybe put if just below the const server2 =
|
||
// test for immutable `opts` | ||
const opts = { foo: 'bar', NPNProtocols: [ 'http/1.1' ] }; | ||
const server1 = https.createServer(opts); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tiny nit: instead of using server1
, server2
, and server3
we can use block scope.
{
// test for immutable `opts`
}
{
// validate that `createServer` can work with the only argument requestListener
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a style we now use more often (helps frame every test case), but IMHO it's up to you...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯
LGTM as is
LGTM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with a comment
'use strict'; | ||
|
||
const common = require('../common'); | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add this:
if (!common.hasCrypto) {
common.skip('missing crypto');
return;
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure. 👌
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with nit
if (!(this instanceof Server)) return new Server(opts, requestListener); | ||
|
||
if (typeof opts === 'function') { | ||
requestListener = opts; | ||
opts = undefined; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor nit: The optional value is an object, but here reset to undefined
, this does not appear consistent :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yorkie, Because I think util._extend({}, undefined)
performance is better than util._extend({}, {})
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then I think you would make the opts
default be unset as well for performance. BTW perf is not that crucial here than consistence and readability, this constructor needn't be called too much times in any of applications :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem is opts = util._extend({}, opts);
shows it's not a consistent.
Do you mean that?
...
const realOpts = util._extend({}, opts);
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The mean problem is the default value, removing that like https://github.com/nodejs/node/pull/13599/files#r121620077 works for me :)
lib/https.js
Outdated
@@ -31,9 +31,15 @@ const inherits = util.inherits; | |||
const debug = util.debuglog('https'); | |||
const { urlToOptions, searchParamsSymbol } = require('internal/url'); | |||
|
|||
function Server(opts, requestListener) { | |||
function Server(opts = {}, requestListener) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that using default values is potentially a breaking change given that it changes the value of Server.length
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shall I delete the default value?
CITGM to look for breakage: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/871/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
if test still pass removing default was a good call
`opts` in `createServer` will be immutable that won't change origional opts value. What's more, it's optional which can make `requestListener` be the first argument. PR-URL: nodejs#13599 Fixes: nodejs#13584 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Yorkie Liu <yorkiefixer@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Brian White <mscdex@mscdex.net>
Landed in c1c2267 |
`opts` in `createServer` will be immutable that won't change origional opts value. What's more, it's optional which can make `requestListener` be the first argument. PR-URL: #13599 Fixes: #13584 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Yorkie Liu <yorkiefixer@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Brian White <mscdex@mscdex.net>
`opts` in `createServer` will be immutable that won't change origional opts value. What's more, it's optional which can make `requestListener` be the first argument. PR-URL: #13599 Fixes: #13584 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Yorkie Liu <yorkiefixer@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Brian White <mscdex@mscdex.net>
`opts` in `createServer` will be immutable that won't change origional opts value. What's more, it's optional which can make `requestListener` be the first argument. PR-URL: #13599 Fixes: #13584 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Yorkie Liu <yorkiefixer@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Brian White <mscdex@mscdex.net>
`opts` in `createServer` will be immutable that won't change origional opts value. What's more, it's optional which can make `requestListener` be the first argument. PR-URL: #13599 Fixes: #13584 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Yorkie Liu <yorkiefixer@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Brian White <mscdex@mscdex.net>
`opts` in `createServer` will be immutable that won't change origional opts value. What's more, it's optional which can make `requestListener` be the first argument. PR-URL: #13599 Fixes: #13584 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Yorkie Liu <yorkiefixer@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Brian White <mscdex@mscdex.net>
Release team decided not to land on v6.x, if you disagree let us know. |
opts
increateServer
will be immutable that won't change origionalopts value. What's more, it's optional which can make
requestListener
be the first argument.
Refs: #13584
Checklist
make -j4 test
(UNIX)Affected core subsystem(s)
https