Skip to content

What does SecureContext::EnableTicketKeyCallback do? #13176

@addaleax

Description

@addaleax

e83a41a introduced an internal enableTicketKeyCallback method on SecureContexts, without documentation or usage in JS land. It’s only mentioned in one of the test files, test/parallel/test-https-resume-after-renew.js. So … Should this functionality stay? Should it go? And generally, what is it?

I stumbled upon this while looking into #13142 (comment) to see whether SecureContext should inherit from AsyncWrap, but I can’t really tell how the MakeCallback there works and whether it should really be one, so I thought it might be good to just ask about it.

@indutny @nodejs/crypto

Metadata

Metadata

Assignees

No one assigned

    Labels

    cryptoIssues and PRs related to the crypto subsystem.questionIssues that look for answers.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions