A Security Application Manager configuration determines the action that will take place when a threat is identified or a request exceeds a rate limit.
A Security Application Manager configuration identifies a traffic profile, the rules that determine how that traffic will be screened, and the enforcement action that will take place when a threat is identified. This enforcement action is defined when you assign an access rule or managed to a Security Application Manager configuration. The user experience for each possible configuration is described below.
Configuration | Description |
---|---|
Alert |
Our service treats the request as if it had not been screened. The client will be unaware that the request was screened by WAF. |
Block |
The user experience for requests blocked by WAF is described below.
Default WAF response header name/value: X-EC-Security-Audit: 403
|
Custom Response |
Our service provides a custom response to identified threats. This custom response is defined within a Security Application Manager configuration when setting up access rules and managed rules. It defines the response headers, body, and status code that will be sent to the user. |
Upon exceeding a rate limit, your Security Application Manager configuration determines the action that will be applied to eligible requests. The user experience for each possible configuration is described below.
Configuration | Description |
---|---|
Alert Only |
Alerts do not alter the user experience. Our service treats the request as if it had not exceeded the rate limit. |
Custom Response |
Our service provides a custom response to rate limited requests. This custom response is defined within a Security Application Manager configuration when setting up rate rules. It defines the response headers, body, and status code that will be sent to the user. |
Drop Request |
Our service sends a 503 Service Unavailable response with a Retry-After header to rate limited requests. |
Redirect (HTTP 302) |
Our service redirects rate limited requests to a predefined URL. The client will receive the response for the resource located at that URL and a 302 Found. |
Edgecast CDN