500 on very long URLs instead of pages or 414

[DorianNiemiecSVRJS]

Title: 500 error on very long URLs instead of serving static pages or 414 error
Platform/Software Version: SVR.JS 3.4.21 or older, 3.7.1 or older
Steps to Reproduce:

1. Install SVR.JS
2. Enable HTTPS and HTTP/2
3. Start SVR.JS
4. Visit very long URL page (without query string) using HTTP/2, for example https://forum.svrjs.org/abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz

Expected Behavior: Static file served, 404 Not Found or 414 URI Too Long error.
Actual Behavior: 500 Internal Server Error with ENAMETOOLONG code in JavaScript error stack
Additional Information:
This bug is reproduced, if HTTP/2 is enabled, since Node.JS will not emit clientError event in case of those URLs. If HTTP/2 is not enabled, Node.JS will emit clientError event and SVR.JS will return 414 URI Too Long or other client error. If significant length is in query string, the bug wouldn't be triggered.

[DorianNiemiecSVRJS]

Thank you for bug report! I did fix it in SVR.JS 3.4.22 and SVR.JS 3.7.2.