Prevents the tunnel from crashing when invalid headers are detected [Issue #425 fix]

[alwayshopeless]

Handling exception of failed header parsing when logging a request.

Hotfix for an issue that prevents the tunnel from crashing when invalid headers are detected.

TODO: align error log output to your default logger.
Related to Issue #425

[what-the-diff]

PR Summary

• Included Additional Dependencies:
  New import statements have been added. These will allow the program to properly utilize functions from Illuminate\Support\Facades's Log, as well as Laminas\Http\Header\Exception's RuntimeException.

• Improved Error Management and Tracking:
  The logRequest method has been wrapped within a try-catch block. This means that the program will actively try to execute the logRequest method, but if it encounters any errors (specifically a RuntimeException), it will "catch" this event and log the error message using Laravel's logging system. This enhancement improves the handling of unforeseen issues and makes it easier to identify and fix them down the line.

[mpociot]

Do you know when exactly invalid headers are detected? Would be great to have a test case for this and handle this better in the logger

[alwayshopeless]

Do you know when exactly invalid headers are detected? Would be great to have a test case for this and handle this better in the logger

Please look at my issue #425, I have attached a stack trace and an example of how to reproduce the error

[alwayshopeless]

Technically, we will 100% have a bunch of unhandled exceptions in the future for one reason or another if the request logger exceptions are not handled, this happens when parsing headers, getting domain names, etc., probably all of them cause the tunnel to crash (but this is my guess)

Until a better solution is thought out, it would be preferable for the invalid request to still be sent to the target server, but for the tunnel itself not to fail, but to log errors