CDN edge response integrity
105-cdn-edge-response-integrity.yaml
HTTP(S)
What this example does
This example demonstrates cdn edge response integrity.
Checks and behavior
- Sends an GET request to https://static.example.com/assets/app.css.
- Checks allowed/denied HTTP status codes.
- Validates required, forbidden or matching HTTP headers.
- Validates redirect behavior and destination constraints.
- TLS settings cover certificate trust, certificate expiry.
- Applies response-time thresholds for operational alerting.
- Formats results for nagios output.
Adapt example domains, addresses, credentials and thresholds to your environment before use.
YAML configuration
# Copyright (c) 2026 mati peterson. Maintainer: mati peterson <ipsonic@mailbox.org>. Project: https://ipsonic.com/probe/. Disclaimer: Provided AS IS, without warranty of any kind. Use at your own risk; validate checks and configurations before production use.
# CDN edge smoke test: HTTPS, expected media type, bounded body size, latency.
# Do not assert vendor-specific headers unless they are part of your contract.
name: "CDN edge response integrity"
url: "https://static.example.com/assets/app.css"
request: {method: GET, follow_redirects: true}
timeouts: {connect: 3, response: 10}
tls: {verify: true, min_valid_days: 14}
tests:
status: {allow: [200]}
redirects:
require_https: true
max_count: 2
allowed_hosts: [static.example.com]
response:
min_bytes: 10
max_bytes: 524288
content_type: text/css
headers:
contains:
Content-Type: [text/css]
monitoring:
service_name: "CDN CSS Asset"
output: nagios
on_failure: critical
thresholds:
response_time: {warning: 1, critical: 3}