On Tue, 4 Aug 2026 15:22:24 GMT, Guanqiang Han <[email protected]> wrote:
>> Please review this change. Thanks! >> >> **Description:** >> >> When an oversized CRL is fetched, the cached `crl` is cleared only when >> debugging is enabled, and `lastModified` is not reset. >> >> **Solution:** >> >> Always clear the cached `crl` and reset `lastModified` when an oversized CRL >> is discarded. >> >> --------- >> - [x] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > Guanqiang Han has updated the pull request incrementally with one additional > commit since the last revision: > > Handle null CRLs in getMatchingCRLs Hmmm...there are a series of tests that involve cert path validation that are failing after this new change. However it appears that they're failing with network errors between the cert path validator and target servers. Given that it's in the larger cert path validation suite of tests, I'd like to re-run those tests to determine whether they are due to an infrastructure failure or this new logic in URICertStore. ------------- PR Comment: https://git.openjdk.org/jdk/pull/32164#issuecomment-5194036874
