Does not handle an invalid timezone offset well

The following message [1] has the date:

Date: Tue, 13 Jul 2004 17:09:05 -429496729500

This does not appear to be even a valid obsolete TZ specification.
As such, according to RFC2822/4.3 it should be considered as -0000.

The date appears as follows in the display:

Date: NaN-NaN-NaN NaN:NaN (+0100)

Where the date cannot be converted, it would be better to leave it as is.

[1] https://lists.apache.org/thread.html/d5d736fb78e5d99fcd9840dbfb6c21fc256bafad0864f301b9190490@15462972000545@%3Cdev.lucene.apache.org%3E

Reproduce the malformed Date header from the issue and trace the date parsing and display path in the repository; the payload names no specific file or test. Done means an invalid timezone offset is handled according to RFC 2822 as -0000, or the original date is left unchanged instead of rendering NaN values.

Written by the indexing model from the issue text.