1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
//! HTTPS transport binding for the Trust Tasks framework.
//!
//! Implements [SPEC.md §9](../../../SPEC.md#9-transport-bindings) over HTTP/1.1
//! using axum on the server side and reqwest on the client side. The binding
//! authenticates parties via an `Authorization: Bearer <token>` header that
//! maps to a Verifiable Identifier — sufficient for demos, mockups, and
//! end-to-end testing without standing up an mTLS or DIDComm stack.
//!
//! ## Binding URI
//!
//! `https://trusttasks.org/binding/https/0.1`
//!
//! ## On the wire
//!
//! ```text
//! POST /trust-tasks HTTP/1.1
//! Host: example.com
//! Content-Type: application/json
//! Authorization: Bearer <token>
//!
//! {
//! "id": "...",
//! "type": "https://trusttasks.org/spec/acl/grant/0.1",
//! "issuer": "did:web:org.example",
//! "recipient": "did:web:maintainer.example",
//! "issuedAt": "2026-05-17T10:00:00Z",
//! "payload": { ... }
//! }
//! ```
//!
//! The server maps the bearer token to a VID, runs the §7.2 / §4.8.1
//! consumer-side validation pipeline (cross-checking the in-band `issuer`
//! against the authenticated sender), and dispatches the document to the
//! handler registered for its `type` URI.
//!
//! ## Cargo features
//!
//! * `server` (default) — pulls in axum + tokio + tower; exposes
//! [`HttpsServer`].
//! * `client` (default) — pulls in reqwest; exposes [`HttpsClient`].
//!
//! Disable one or the other if your binary only acts as a producer or only
//! as a consumer.
pub use ;
pub use TransportError;
pub use ;
pub use status_for_code;
pub use ;
pub use ;