A client of an RFC 3161 time-stamp authority over HTTP, through the HttpClient it is given: it time-stamps signatures (PAdES B-T, through TimestampClient) and documents (Timestamp(Stream, PdfTimestampClient, String?)).
public sealed class PdfTimestampClient
RFC 3161 §2.4 and §3.4 (time-stamp protocol via HTTP), as updated by RFC 5816; ISO 32000-2 §12.8.3.3.1 (timestamp information as an
unsigned attribute), §12.8.3.4.3 b) (the PAdES signature timestamp) and §12.8.5 (document timestamps). A request is a
TimeStampReq of the hash of the data with DigestAlgorithm, a fresh random nonce, Policy when
set, and certReq true, so the token carries the authority's certificate; it is POSTed to AuthorityUri as
application/timestamp-query. The response must grant the request and hold a token whose message imprint, nonce and policy
are the request's; anything else throws PdfTimestampException, and nothing is written. The token's signature and
the authority's certificate path are not validated here: validating signatures does that.
The HttpClient is the transport: its handler decides how the request travels (proxies, authentication, retries), and a test can give it a handler that answers in process. The client does not dispose it. The synchronous Sign(Stream, IPdfSigner, PdfSignatureOptions?) and Timestamp(Stream, PdfTimestampClient, String?) send the request with , which the browser does not support: use the asynchronous methods there. A client may be shared between threads and documents.
kind:method, kind:property, kind:ctor. Press Esc to clear.PdfTimestampClient(HttpClient, Uri)Initializes a new instance of the PdfTimestampClient class.AuthorityUriGets the time-stamp authority's HTTP endpoint.DigestAlgorithmGets or sets the hash algorithm of the message imprint: SHA-256 (the default), SHA-384 or SHA-512, or a SHA-3 algorithm where signing supports it. The authority must accept it.PolicyGets or sets the object identifier of the policy to ask the authority to issue tokens under (reqPolicy), in dotted form; null (the default) accepts the authority's default policy.TokenSizeEstimateGets or sets how many bytes to reserve in the signature's Contents for the token, which is only known once it arrives, after the byte range is fixed: 8192 by default, enough for an authority certificate and its issuers. A token that does not fit throws InvalidOperationException and nothing is written; raise this for an authority with a long chain.