aws-lc ocsp workaround - #22694
Closed
icing wants to merge 1 commit into
Closed
aws-lc ocsp workaround#22694icing wants to merge 1 commit into
icing wants to merge 1 commit into
Conversation
SSL_get_tlsext_status_ocsp_resp() is documented to return -1 on a missing OCSP stapling from the server, however AWS-LC is breaking that by returning 0. Since it does not semantically make a difference if the data is reported missing or has 0 length, treat 0 also as a missing stapling.
bagder
approved these changes
Aug 26, 2026
|
Analysis of PR #22694 at a9279993: Test 322 failed, which has NOT been flaky recently, so there could be a real issue in this PR. Note that this test has failed in 12 different CI jobs (the link just goes to one of them). Generated by Testclutch |
bagder
approved these changes
Aug 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
SSL_get_tlsext_status_ocsp_resp() is documented to return -1 on a missing OCSP stapling from the server, however AWS-LC is breaking that by returning 0.
Since it does not semantically make a difference if the data is reported missing or has 0 length, treat 0 also as a missing stapling.