HTTP Header Diff Monitor

Store Positioning

Store title: HTTP Header Diff Monitor

Short description: Compare previous/current HTTP headers and show exact added/removed/changed security/cache/CORS headers.

SEO title: HTTP Header Diff Monitor — change monitoring and diff reports

SEO description: Compare previous/current HTTP headers and show exact added/removed/changed security/cache/CORS headers. Use it for recurring watchlists, previous/current comparisons, changed-row evidence, and schedule-friendly digests.

Categories: AUTOMATION

Keywords: http, header, diff, monitor, change monitor, security headers, recurring monitor/diff actor

Fixed-Inclusive PPE Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

• Tier: M1 — Recurring monitor/diff actor
• Primary event: snapshot-compared at $0.00650 base
• Default max charge: $20.00
• Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

• actor-start: base $0.02000, GOLD $0.01600. HTTP Header Diff Monitor: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• snapshot-compared: base $0.00650, GOLD $0.00520. HTTP Header Diff Monitor: charged when snapshot compared is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• change-detected: base $0.01300, GOLD $0.01040. HTTP Header Diff Monitor: charged when change detected is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• digest-generated: base $0.05000, GOLD $0.04000. HTTP Header Diff Monitor: charged when digest generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• executive-report-generated: base $0.10000, GOLD $0.08000. HTTP Header Diff Monitor: charged when executive report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

Public Task Concepts

• Monitor HTTP Header Diff Monitor changes on a schedule
• Compare previous and current HTTP Header Diff Monitor snapshots
• Audit http issues across supplied public inputs
• Extract evidence-backed http rows for client QA
• Create a change digest for HTTP Header Diff Monitor

What It Does

Compare previous/current HTTP headers and show exact added/removed/changed security/cache/CORS headers.

This local package is part of the Junipr Apify actors 171-200 premium build for ChatGPT review.

What It Does Not Do

• It does not call live Apify APIs.
• It does not publish, upload Store assets, create public tasks, or configure live PPE.
• It does not claim publish readiness.
• It does not make unbounded network calls in the supplied examples path.

Input Fields

Seed shape: inputItems, maxItems, includeReport

The tiny fixture is available at examples/input.tiny.json and mirrored at fixtures/input.tiny.json for the local runner.

Output Fields

• url
• headerName
• changeType
• oldValue
• newValue
• category
• severity
• evidence
• recommendation

Public Task Examples

Compare HTTP security headers between releases

• Search intent: compare http security headers between releases
• Specific input: Fixture input shaped for compare http security headers between releases.
• Expected output: Dataset rows with url, headerName, changeType, oldValue plus local KVS report evidence.
• Why run it: DevOps, AppSec, web teams, agencies would run this to get a bounded local proof before any live Apify review or production use.

Find removed HSTS headers in a deployment diff

• Search intent: find removed hsts headers in a deployment diff
• Specific input: Fixture input shaped for find removed hsts headers in a deployment diff.
• Expected output: Dataset rows with url, headerName, changeType, oldValue plus local KVS report evidence.
• Why run it: DevOps, AppSec, web teams, agencies would run this to get a bounded local proof before any live Apify review or production use.

Detect newly added CSP headers in fixture responses

• Search intent: detect newly added csp headers in fixture responses
• Specific input: Fixture input shaped for detect newly added csp headers in fixture responses.
• Expected output: Dataset rows with url, headerName, changeType, oldValue plus local KVS report evidence.
• Why run it: DevOps, AppSec, web teams, agencies would run this to get a bounded local proof before any live Apify review or production use.

Summarize changed server headers for QA

• Search intent: summarize changed server headers for qa
• Specific input: Fixture input shaped for summarize changed server headers for qa.
• Expected output: Dataset rows with url, headerName, changeType, oldValue plus local KVS report evidence.
• Why run it: DevOps, AppSec, web teams, agencies would run this to get a bounded local proof before any live Apify review or production use.

Create header regression rows for release notes

• Search intent: create header regression rows for release notes
• Specific input: Fixture input shaped for create header regression rows for release notes.
• Expected output: Dataset rows with url, headerName, changeType, oldValue plus local KVS report evidence.
• Why run it: DevOps, AppSec, web teams, agencies would run this to get a bounded local proof before any live Apify review or production use.

Tests

• Actor-specific fixture tests live in test/http-header-diff-monitor.test.ts.
• Node-based local suites validate dataset schema conformance, output samples, local smoke runs, and PPE guard behavior.

FAQ

Is this live on Apify?

No. This is a local package for ChatGPT review only.

Is it publish-ready?

No. It needs later live tiny-run validation and console configuration before any publication decision.