Skip to main content
Version: 1.2.0

HTTP Status

Enrich Web Standards

Synopsis​

Converts HTTP status codes to their corresponding human-readable status names and descriptions based on RFC specifications and extended server implementations.

Schema​

- http_status:
    description: <text>
    field: <ident>
    target_field: <ident>
    if: <script>
    ignore_failure: <boolean>
    ignore_missing: <boolean>
    on_failure: <processor[]>
    on_success: <processor[]>
    tag: <string>

Configuration​

The following fields are used to define the processor:

FieldRequiredDefaultDescription
fieldYField containing the HTTP status code
target_fieldNSame as fieldField to store the status name
descriptionN-Explanatory notes
ifN-Condition to run
ignore_failureNfalseSee Handling Failures
ignore_missingNfalseContinue processing if the field is missing
on_failureN-See Handling Failures
on_successN-See Handling Success
tagN-Identifier

Details​

The processor accepts HTTP status codes in various formats (string, integer, float) and converts them to standardized status names. It supports a comprehensive range of status codes including:

  • Standard RFC codes: All official HTTP status codes from RFC 7231, 7232, 7233, 7234, 7235
  • Informational (1xx): Continue, Switching Protocols, Processing, Early Hints
  • Success (2xx): OK, Created, Accepted, No Content, Partial Content
  • Redirection (3xx): Moved Permanently, Found, Not Modified, Temporary Redirect
  • Client Error (4xx): Bad Request, Unauthorized, Forbidden, Not Found, Method Not Allowed
  • Server Error (5xx): Internal Server Error, Bad Gateway, Service Unavailable, Gateway Timeout
  • Extended codes: IIS-specific subcodes (400.1, 404.1, etc.), CDN-specific codes, and load balancer codes
info

This processor includes extended status codes from popular web servers (IIS, Apache, Nginx), CDNs (Cloudflare, AWS), and load balancers for comprehensive web traffic analysis.

note

The processor supports both integer status codes (200, 404) and decimal subcodes (400.1, 500.19) commonly used by Microsoft IIS and other enterprise web servers.

tip

Use this processor in web access log analysis to make status codes more readable in dashboards and reports. It's particularly useful for identifying specific error conditions through detailed subcode descriptions.

Examples​

Basic Status Code Conversion​

Convert a successful HTTP response...

{
  "status_code": 200
}
- http_status:
    field: status_code

to its readable name:

{
  "status_code": "OK"
}

Client Error Identification​

Identify client errors...

{
  "response_status": "404"
}
- http_status:
    field: response_status
    target_field: error_description

with descriptive names:

{
  "response_status": "404",
  "error_description": "Not Found"
}

Server Error Analysis​

Analyze server errors...

{
  "http_status": 500
}
- http_status:
    field: http_status
    target_field: server_error_type

for troubleshooting:

{
  "http_status": 500,
  "server_error_type": "Internal Server Error"
}

IIS Extended Status Codes​

Handle IIS-specific subcodes...

{
  "iis_status": "400.1"
}
- http_status:
    field: iis_status

with detailed error descriptions:

{
  "iis_status": "Invalid Destination Header"
}

Authentication Failures​

Detailed authentication error analysis...

{
  "auth_status": "401.1"
}
- http_status:
    field: auth_status
    target_field: auth_failure_reason

showing specific failure reasons:

{
  "auth_status": "401.1",
  "auth_failure_reason": "Logon failed"
}

Rate Limiting Detection​

Identify rate limiting responses...

{
  "api_response": 429
}
- http_status:
    field: api_response
    target_field: throttle_status

for API monitoring:

{
  "api_response": 429,
  "throttle_status": "Too Many Requests"
}

CDN and Load Balancer Codes​

Handle CDN-specific status codes...

{
  "cloudflare_status": 520
}
- http_status:
    field: cloudflare_status

for infrastructure monitoring:

{
  "cloudflare_status": "Web Server Returned an Unknown Error"
}

SSL/TLS Error Identification​

Identify SSL/TLS related errors...

{
  "ssl_error": 525
}
- http_status:
    field: ssl_error
    target_field: ssl_issue

for security analysis:

{
  "ssl_error": 525,
  "ssl_issue": "SSL Handshake Failed"
}

WebSocket Connection Issues​

Handle WebSocket-specific errors...

{
  "ws_status": "400.11"
}
- http_status:
    field: ws_status
    target_field: websocket_error

for real-time application monitoring:

{
  "ws_status": "400.11",
  "websocket_error": "Invalid WebSocket request"
}

Unknown Status Codes​

Unrecognized status codes...

{
  "custom_status": 999
}
- http_status:
    field: custom_status

default to "Unassigned":

{
  "custom_status": "Unassigned"
}