fix: close socket when client error handled

[liuweifeng]

Description

According to the Node.js docs, the default behavior of the event clientError is try close the socket with a http code 400 or 431.

If the socket is not closed, it will cause the page to hang in some cases.

Additional context

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the Commit Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[sapphi-red]

Thank you for the PR!

I wasn't aware of this.
https://nodejs.org/api/http.html#event-clienterror:~:text=The%20default%20action%20of%20calling%20.destroy()%20on%20the%20socket%20will%20no%20longer%20take%20place%20if%20there%20are%20listeners%20attached%20for%20%27clientError%27.