HPDFNormalizeHeadlessOCSPResponse Function
Declared in HPDFHeadlessRevocationInfo, this function extracts the BasicOCSPResponse DER carried by a complete successful OCSPResponse
Declaration
function HPDFNormalizeHeadlessOCSPResponse(const DER: SysUtils.TBytes;
MaximumBytes: Integer;
CancellationToken: THPDFCancellationToken): SysUtils.TBytes;Parameters and result
| Parameter | Meaning |
|---|---|
| DER | A complete, non-empty OCSPResponse DER value with successful responseStatus and the id-pkix-ocsp-basic response type |
| MaximumBytes | A positive limit on the input byte count, checked before copying the contained response |
| CancellationToken | An optional token checked before parsing; a requested cancellation raises EHPDFOperationCancelled |
| Result | The contained BasicOCSPResponse DER bytes in a separate dynamic array |
Validation boundary
Malformed, truncated, noncanonical, unsuccessful, unsupported-response-type or trailing DER data raises EHPDFHeadlessRevocationInfoError; empty input, nonpositive limits or oversized input raises the same exception
The function validates the OCSPResponse envelope and extracts its contents; it does not authenticate the BasicOCSPResponse signature, issuer, responder authorisation, certificate status, evidence time or trust chain
Use HPDFValidateHeadlessLTVEvidence or HPDFVerifyHeadlessCMS for those cryptographic and policy checks before treating any evidence as valid
Signing integration
HPDFReadHeadlessRevocationInfo returns complete OCSPResponse values for LTV validation, whilst THPDFCMSSignOptions.AdobeOCSPsDER requires BasicOCSPResponse values; normalise each complete response before passing it to that CMS signed-attribute builder
A BasicOCSPResponse supplied directly as DER is not a complete OCSPResponse and is rejected
Refer to Windows Signed Revocation Information for the JSON signing workflow and Headless Signed Revocation Information for the native evidence workflow