Prashant Bansal

Hi maintainers, I'd like to work on this issue and propose a solution. Could you please assign this task to me? Thank you!

@jasnell @targos @lpinca Please review my pull request when you have a chance. Thank you!

Hey @mcollina , Thanks for your feedback on the keep-alive timeout. I’ve chosen 60 seconds to align with defaults used by major cloud load balancers like AWS ELB/ALB, ensuring broad...

@mcollina , I've resolved this issue and removed the breaking change alert regarding http.Server.keepAliveTimeout. The documentation now reflects the correct status, in line with the release team's guidance. Please review...

Okay, sure—that makes sense. Is 72 seconds sufficient to account for those network delays, or do you recommend going even higher? Happy to adjust as needed based on your experience.

Thanks for clarifying. I’m fine with 65 seconds if that works better—happy to update the default to 65 to provide a bit more buffer over 60. Let me know if...

@mcollina Yes, I’ll address the failing tests and linting issues—just need a bit of time to work through them.

Hello @mcollina, Thank you for your review. I’ve addressed the changes you requested and updated the commit message to fully comply with our guidelines. I’m still a bit uncertain about...

Hi! I noticed that in the Quickstart documentation, the example compares r1.text == r2.text and expects True. However, httpbin.org adds a header ("X-Amzn-Trace-Id") to each response, which changes on every...