Fix a bug where cookies with Max-Age too big are not stored

[duonglaiquang]

This PR does the following

Fix HtmlUnitMaxAgeHandler to correctly handle cookies with large, negative, or non-numeric max-age values per RFC 6265.

Problem

When a server sends a cookie with a max-age value that exceeds Integer.MAX_VALUE (e.g max-age=99999999999), Integer.parseInt throws NumberFormatException, which is wrapped into MalformedCookieException, causing the entire cookie to be rejected.

Per RFC 6265, large values should be capped to a limit (400 days) rather than rejected.

Additionally, negative/zero delta-seconds should set expiry to the earliest representable date instead of offsetting current time.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rbri]

@duonglaiquang will work on that later today, maybe i can add a unit test.

@duonglaiquang do you need a release for all that? As i'm working towards 5.0, no 4.x releases are planned and the 5.0 might need some more time.

and last - have you seen my email?

[duonglaiquang]

@rbri Thank you very much.
All of these are fixes i have already patched on my end so an immediate release is not needed. I will be looking forward to the next big version 😄

[rbri]

hope the java17 move is ok for you

[atnak]

Oh I didn't realise we'd upstreamed all these PRs 😅 Cool 👍

hope the java17 move is ok for you

@rbri
It's another on a growing list of reasons for us to upgrade, so yeah.. we're seriously considering upgrading

[rbri]

@atnak - see https://github.com/HtmlUnit/htmlunit/blob/master/src/changes/changes.xml there are hopefully many more good reasons to move ;-)