Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 34.3k
quic: refactor ocsp handling#34498
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
quic: refactor ocsp handling #34498
Uh oh!
There was an error while loading. Please reload this page.
Conversation
jasnell commented Jul 23, 2020 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
jasnell commented Jul 27, 2020
Ping @nodejs/quic ... this is ready for review. Limited the PR to just the OCSP handling for now. Still working through the issues around client hello, SNI, and |
nodejs-github-bot commented Jul 27, 2020 • edited by jasnell
Loading Uh oh!
There was an error while loading. Please reload this page.
edited by jasnell
Uh oh!
There was an error while loading. Please reload this page.
| // TODO(@jasnell): Proper error | ||
| state.handshakeCompletePromiseReject( | ||
| newERR_OPERATION_FAILED('Handshake failed')); | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can I disagree about these TODOs being irrelevant now? ERR_OPERATION_FAILED is too generic imo, because an operation failing is just about the definition of an error :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know we've had a conversation about this before when you mentioned that our errors are too specific in cases. Struggling to find the right balance. Do you have a more concrete suggestion?
nodejs-github-bot commented Jul 27, 2020
jasnell commented Jul 27, 2020
Landed in 62198d2...1f94b89 |
PR-URL: #34498 Reviewed-By: Anna Henningsen <[email protected]>
PR-URL: #34498 Reviewed-By: Anna Henningsen <[email protected]>
PR-URL: #34498 Reviewed-By: Anna Henningsen <[email protected]>
First two commits are cleanup.
Third commit refactors the OCSP handling, converting it from a callback-oriented event to a configuration-based async function, which makes a lot more sense given that it's only ever called once at a very specific point in the
QuicSessionlifecycle.Fourth commit removes the'clientHello'event. Use cases supporting the event are tenuous at best and do not justify the additional machinery necessary for it to work.Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes