Bug fix on IncorrectContentLength.bambda

[BugBountyzip]

An exception was thrown while running your Bambda for item number 2

java.lang.NumberFormatException: Cannot parse null string
	at java.base/java.lang.Integer.parseInt(Integer.java:627)
	at java.base/java.lang.Integer.parseInt(Integer.java:781)

The original script faced an issue where it attempted to parse the Content-Length header value as an integer without checking if the header was actually present. This led to a NumberFormatException when the header was missing, as it tried to parse a null string.

To fix this, I added a check to ensure that the Content-Length header exists before parsing it. If the header is missing, the script skips the parsing step, thereby avoiding the NumberFormatException. Additionally, I included a try-catch block to gracefully handle any potential number format exceptions that might occur if the header value is not a valid integer. This made the script more robust and error-resistant.

Bambda Contributions

• Bambda has a valid header, featuring an @author annotation and suitable description
• Bambda compiles and executes as expected
• Only .bambda files have been added or modified (README.md files are automatically updated / generated after PR merge)

[PortSwiggerWiener]

Thanks for the bug fix! We've kept the exception throwing if the NumberFormatException is thrown as this is potentially interesting.

Good job 👍

[ps-porpoise]

👍