Enum ProxyProfile

The three shipped profiles, per the plan's "Rollout, profiles and documentation" section. Selecting a profile via Profile applies its ProxyProfileSettings atomically to resource limits, policy modes, TLS protocols, private-network blocking, admission caps, and deadline-second properties, so a caller can never observe a half-applied profile.

Namespace: Titanium.Web.Proxy.Options

Assembly: Titanium.Web.Proxy.dll

Syntax

public enum ProxyProfile

Fields

Name	Description
Balanced	The default. Lenient toward user traffic - it does not block outbound destinations, does not add rejections beyond the always-enforced framing family, and keeps today's shipped limit values - but strict wherever leniency would let a peer exhaust the proxy: resource families are enforced rather than observed, and TLS is restricted to 1.2/1.3.
LegacyCompatible	Opt-in for 4.x migrators. Permits legacy TLS 1.0/1.1 in addition to TLS 1.2/1.3 (SSL 3.0 is not offered on modern .NET) and relaxes the non-memory families to Observe. The memory-bounding families (BodyBudget, DecompressionRatio) stay enforced even here, since Observe cannot protect against exhaustion. Framing remains enforce-only, as it always is.
PublicFacing	Opt-in for deployments that accept requests from untrusted clients. Balanced plus outbound destination blocking for private, link-local and metadata addresses (BlockPrivateNetworkDestinations) and tighter admission and deadline values (a finite global connection cap and bounded client-header, response-header, idle and total-request deadlines, none of which are bounded by default under Balanced). Header-name hygiene (control-character/CRLF rejection) is already unconditionally enforced under every profile - see the framing family's always-enforce rule - so this profile does not add a separate header-validation mode.