Namespace ProtoTest.Http

Classes

AuthAttribute<TAuthenticator>

Applies an IProtoHttpAuthenticator to the HTTP-based clients of a test, for example [Auth<BearerTokenAuthenticator>("token")]. Several attributes at the same level are ordered by Order and composed.

ProtoApplicationTarget

Records which application a registered HTTP target (client) belongs to, so collectors and other services can resolve the target's application without a separate client configuration section.

ProtoApplicationTargets

Resolves the application a registered target belongs to.

ProtoCompositeHttpAuthenticator

Applies several authenticators in order, tracing each application under a shared source.

ProtoHttpAttachmentOptions

Base options for capturing and redacting HTTP request/response artifacts, shared by the REST and GraphQL integrations so both observe the same capture and redaction rules. Each protocol registers an instance created with its own configuration section.

ProtoHttpAuthLifecycleHook

Resolves the ordered authenticator attributes that apply to a protocol before each test, builds a composite authenticator when more than one applies, and records the resolved configuration as the protocol's auth entity state. The client a test uses is chosen separately by [Application].

ProtoHttpAuthenticationApplier

Resolves and applies (or explicitly skips) authentication for one outgoing HTTP request, shared by every protocol request builder. The outcome is an attribute of the request operation the caller owns, not a separate entry: authentication is part of the request, not a step beside it.

ProtoHttpAuthenticationContext

Context supplied to an HTTP-based authenticator when a request is sent.

ProtoHttpBaseAddressRegistration
ProtoHttpClientAliasRegistration

Maps a protocol target to an HTTP client already owned by the current test.

ProtoHttpClientEndpointRegistration

Records the application endpoint a named HTTP client was registered with, so the resolver can root an in-process transport at the registered path without re-reading the client's initializer.

ProtoHttpClientInitializer

Initializes a named HTTP client from an explicit URL, or from the application the target belongs to: the application's base address, optionally combined with one of its named endpoint paths.

ProtoHttpClientRegistration

Registers the named HTTP client and initializer shared by every HTTP-based protocol's AddClient overloads, so each protocol only supplies its own display label and error text.

ProtoHttpClientResolution

The HTTP client a protocol accessor will use, together with the per-test resolver that supplies its base address and the names requests and traces should use.

ProtoHttpClientResolver

Resolves the HTTP client a protocol accessor uses for the current test, shared by the HTTP-based protocols so their registration and alias lookup, in-process transport fallback, and error text stay identical.

ProtoHttpDiagnosticSanitizer

Redacts sensitive values from HTTP request/response diagnostics before they are traced or attached. Shared by the REST and GraphQL integrations.

ProtoHttpOptionsRegistration

Registers per-protocol response and attachment options under a stable protocol key, so REST and GraphQL keep their own configuration sections even though they share the base option types.

ProtoHttpOptionsResolver

Resolves the response and attachment options a protocol registered under its own key, so REST and GraphQL never share configuration even though they use the same base option types.

ProtoHttpResponseBuffer
ProtoHttpResponseOptions

Controls how HTTP response bodies are buffered, shared by the REST and GraphQL integrations. Each protocol registers an instance created with its own configuration section.

ProtoHttpUri

Platform-independent HTTP URI classification shared by protocol integrations.

ProtoResponseTooLargeException
ProtoTargetBuilder

Shared, protocol-neutral IProtoTargetBuilder for every protocol integration.

Interfaces

IProtoHttpAuthMetadata

Declares, via attribute metadata, an authenticator that an HTTP protocol's lifecycle hook applies to its named client. Protocols keeps protocol hooks from picking up each other's authenticators when a test needs different authentication per protocol.

IProtoHttpAuthenticator

Authenticates an outgoing HTTP request for a REST, GraphQL, or other HTTP-based client.