-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Docs
Looking at PHPC-1671, it appears that our current debugging output:
mongoc: DEBUG > Could not send HTTP request: Failed to connect to: ocsp.int-x3.letsencrypt.org
mongoc: TRACE > GOTO: _contact_ocsp_responder():728 retry
mongoc: TRACE > EXIT: _contact_ocsp_responder():756
mongoc: DEBUG > Soft-fail: No OCSP responder could be reached
Gives the impression that OCSP has failed. We should consider making it more apparent to the user that even though we could not send an HTTP request to an OCSP responder, OCSP succeeded.
- is related to
-
PHPC-1671 Better user-facing messaging when OCSP endpoints are unreachable
- Closed
- related to
-
CDRIVER-3788 DNS Lookup Failures to OCSP Exhausts connectTimeoutMS
- Backlog
-
CDRIVER-4522 Possible improvements to mitigate negative effects of OCSP endpoint timeouts
- Backlog