Enum PolicyFamily
The resource-bound policy families that support an PolicyMode other than
Enforce, per the plan's rollout section. Framing, chunk parsing and
Content-Length/Transfer-Encoding resolution are deliberately not members of this
enum: they are always enforced and never consult a mode, because there is no safe
Observe action for an ambiguous or malformed message - see
ProxyPolicyModes and AllowAmbiguousFraming for the one explicit,
isolated escape hatch from that rule.
Namespace: Titanium.Web.Proxy.Options
Assembly: Titanium.Web.Proxy.dll
Syntax
public enum PolicyFamily
Fields
| Name | Description |
|---|---|
| AdmissionControl | The global and per-endpoint admission gates that bound concurrently admitted client connections. |
| BodyBudget | Cumulative whole-body buffering limits ( |
| DecompressionRatio | The compressed-input/decompressed-output byte budgets and the expansion-ratio ceiling
(MaxDecompressionRatio) applied while draining a
Today, that decoded-byte cap is exactly what protects this case in practice: the decompression chain writes into the same Titanium.Web.Proxy.Network.Streams.BoundedWriteStream- wrapped target BodyBudget already bounds, so a small compressed body that expands enormously is caught the moment the decoded output crosses that limit, without needing a separately computed ratio. MaxDecompressionRatio and the encoded/decoded byte pair remain reserved for a future, more precise per-stream computation; this family's mode exists now so a profile can name it, but changing it has no additional effect while BodyBudget already covers the same paths. |
| HeaderLimits | Header line length, header count and aggregate header-byte limits (MaxHeaderLineBytes/MaxHeaderCount/ MaxHeaderAggregateBytes) intended for the request/response header-block read.
Reserved, like DecompressionRatio, for numeric enforcement not yet wired
to every header-reading call site; this family's mode exists so a profile can name it
ahead of that work landing. The client request-line/header deadline (a
different, already-enforced protection - see |
| Http2AbuseBudget | HTTP/2 abuse budgets: the open-header-block CONTINUATION frame-count/wall-clock bound and the peer-initiated incomplete-stream-reset budget. |