Enforcement-Action
Make the selected action visible.
Enforcement-Action is a proposed advisory HTTP response field for communicating an already-selected local enforcement action between cooperating components.
An Internet-Draft proposal. Not an adopted HTTP standard.
One selection.
Three ways to observe it.
The application selects monitor in every example. Responses remain 200 OK to isolate field visibility.
Request path: Edge → Gateway → Application
Response path shown below ↓
01 Implicit
The selection stays local.
02 Explicit
The reported token is preserved.
03 Strip
The gateway observes, then removes the field.
monitor represents Enforcement-Action: monitor. In strip mode, the gateway removes the field before it reaches the edge outside the trusted boundary. No field does not mean allow.Conceptual illustration—not an executed experiment or proof that monitoring occurred.
Explore the measurement method →Expose an action through a response field.
Study what participating components can see.
Evaluate visibility alongside signaling cost.
Choose your next step.
Specification
Understand the advisory field, explore an illustrative response, and read the draft.
02Measurement
Study selected-action visibility at named HTTP observation points.
03Results
Understand which experimental records are available and what they can support.
04Contribute
Help refine the protocol question, implementation behavior, and measurement method.
Explore the engine research.
Architecture, documented local results, and an illustrative application security demonstration. The Enforcement-Action proposal can be evaluated independently of this engine.