You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug description
As you stated in the README, I'm getting this error only when ENV=production.
I do need that because I'm trying this tool, which looks great, for performance tests.
Reason why I'm opening this issue is that I'm running node 12.14, which is fairly new!
This is a known bug of the spdy library. This is the reason I don't use http2 by default but only in production mode. Unfortunately, there aren't any news about a possible fix neither we know under which conditions it occurs. I'm not able to reproduce the bug to fix the library.
At the moment, the only fix is to avoid the production environment. If you need production in you context you can workaround in the following way.
In version 5 of https-localhost I planned to stop using express. This will allow to use the new built-in http2 instead of spdy, since express doesn't support http2 yet.
Hopefully, v5 should come in March 2020.
If you don't need express either, take a look to Use with a web framework different from Express.js. Just use http2 instead of https in the example code.
There are no changes that you can use express in this way, but take a look to koajs, it should work and it is newer and lighter.
Feel free to reopen this issue if my answer does not satisfy your questions
Bug description
As you stated in the README, I'm getting this error only when
ENV=production
.I do need that because I'm trying this tool, which looks great, for performance tests.
Reason why I'm opening this issue is that I'm running node 12.14, which is fairly new!
To Reproduce
server.js
Expected behavior
not
RangeError: Invalid typed array length: -4095
System information (please complete the following information):
The text was updated successfully, but these errors were encountered: