-
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
highWaterMark option is ignored in HTTPs request stream #32781
Comments
I'm try working on this. |
PR-URL: #32786 Fixes: #32781 Reviewed-By: Zeyu Yang <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Andrey Pechkurov <[email protected]>
PR-URL: #32786 Fixes: #32781 Reviewed-By: Zeyu Yang <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Andrey Pechkurov <[email protected]>
PR-URL: #32786 Fixes: #32781 Reviewed-By: Zeyu Yang <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Andrey Pechkurov <[email protected]>
PR-URL: #32786 Fixes: #32781 Reviewed-By: Zeyu Yang <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Andrey Pechkurov <[email protected]>
There is still something strange... Testing with Node.js v15.0.0-nightly20200505c17dcb3253 it returns fine now the highWaterMark in https module but it is still downloading with chunks of 16Kb
Testing the same file to download, to the same server in a LAN with http instead https we are receiving in "on data" callback bigger chunks
Should I fill a new ticket? |
I'm trying to replicate this problem. |
@thunderol could you create a separate GH issue? It'll be easier to track the fix this way. |
Created new issue #33262 |
Hi,
https request stream ignores the custom highWaterMark size option. In http request it works perfectly.
Version: All of them, even nightly
Platform: Windows 10 64-bit
Platform: https
What steps will reproduce the bug?
Execute the following code snippet using node
How often does it reproduce? Is there a required condition?
No. This potential bug can always be reproduced.
What is the expected behavior?
https stream readableHighWaterMark should be 128000 instead 16384.
What do you see instead?
Console Output:
The text was updated successfully, but these errors were encountered: