-
Notifications
You must be signed in to change notification settings - Fork 12k
Ref #7197 - Increase keepAliveTimeout for Webpack Dev Server #7563
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
Conversation
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed, please reply here (e.g.
|
I signed it! |
CLAs look good, thanks! |
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.
Thanks for implementing this fix 👍
The CI is failing only because of the commit name. Can you change it to fix(@angular/cli): Increase keepAliveTimeout for Webpack Dev Server
please?
You're welcome. I've reworded the commit message to your suggestion. Let me know if there's anything else I can do. |
I think that was the only thing missing. We can merge after CI is green. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Fixes #7197
This resolves an issue with browsers throwing
net::ERR_CONTENT_LENGTH_MISMATCH
for large files or slow connections, when using Webpack Dev Server. Large files, such as a vendor javascript bundle, are susceptible to this bug which is tracked all the way back to the NodeJS http module. A change in NodeJS 8.0 broke thekeepAliveTimeout
handling where active requests don't reset the timeout timer. This is fixed in NodeJS 8.5.The
keepAliveTimeout
defaults to 5 seconds, which may be too short. This change increases thatkeepAliveTimeout
to 30 seconds, but only if the Node process has versions between 8.0 - 8.4.I'd like to mention, I don't use Angular CLI and haven't tried this fix with Angular CLI specifically. I have however verified it works when using Webpack Dev Server standalone.