Modify HTTP header log settings

put

https://{hostname}/appsec/v1/configs/{configId}/versions/{versionNumber}/security-policies/{policyId}/advanced-settings/logging

All products Enable, disable, or update HTTP header logging settings for a specific policy. This operation applies at the security policy level, and overrides the HTTP header log settings at the configuration level on a per-policy basis.

Path Params

configId

int64

required

A unique identifier for each configuration.

versionNumber

integer

required

A unique identifier for each version of a configuration.

policyId

string

required

A unique identifier for a security policy.

Query Params

accountSwitchKey

string

For customers who manage more than one account, this runs the operation from another account. The Identity and Access Management API provides a list of available account switch keys.

Body Params

allowSampling

boolean

Whether you enabled the header data sampling.

object

When enabled, filter requests whose headers you log by cookie.

customHeaders

object

When enabled, filter requests you log by custom headers you specify.

override

boolean

required

When enabled, your security configuration won't log any header data for security events triggered by settings in the security configuration.

standardHeaders

object

When enabled, filter requests you log by standard headers you specify.

Headers

string

enum

Defaults to application/json

Generated from available response content types

Allowed:

Responses

Language

URL

Response

Choose an example:

application/json

application/problem+json

200Successfully updated the policy HTTP Header Logging settings:.

400Invalid. Client error, such as invalid or malformed input.

403Forbidden. You don't have permission to write to this resource.

404Not found. The security policy doesn't exist, doesn't carry application layer controls, or no rule with this ID is available for use in this policy.

500Internal server error. Something went wrong on our side. Try again in a few minutes or contact support if the error persists.