Skip to content
Skills Library
DevOps & cloud · Review & audit

conditional-request-behavior-audit

/conditional-request-behavior-audit

Check how validators behave at the edge, since a mismatched etag or not-modified handling can serve stale state or mask an update that already happened at the origin. Use when responses carry validators such as etag or last-modified and the edge participates in revalidation

Repository
edgescout ↗
Licence
MIT
Last repository change
28.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Check how validators behave at the edge, since a mismatched etag or not-modified handling can serve stale state or mask an update that already happened at the origin. Use when responses carry validators such as etag or last-modified and the edge participates in revalidation

Original author description

Check how validators behave at the edge, since a mismatched etag or not-modified handling can serve stale state or mask an update that already happened at the origin. Use when responses carry validators such as etag or last-modified and the edge participates in revalidation

How it works

  1. Procedure
  2. Signals
  3. Patterns
  4. Pitfalls
  5. Done when
  6. References
Original SKILL.md headings · 62 lines, 419 words
SKILL.md preview
---
name: conditional-request-behavior-audit
description: "Check how validators behave at the edge, since a mismatched etag or not-modified handling can serve stale state or mask an update that already happened at the origin. Use when responses carry validators such as etag or last-modified and the edge participates in revalidation"
pack: edgescout
version: 1.0.0
category: web-app
tags: [detect, validators, revalidation]
---

# Conditional Request Behavior Audit

> Check how validators behave at the edge, since a mismatched etag or not-modified handling can serve stale state or mask an update that already happened at the origin

**Use when:** responses carry validators such as etag or last-modified and the edge participates in revalidation

**Avoid when:** the path uses no validators and revalidation never occurs for any tested request

## Procedure

1. Capture the etag and last-modified values from an initial response and record whether the edge reported it as stored.
2. Send a conditional request with the captured validator and record status, headers and cache status token.
3. Modify content through the application's own supported path if permitted, then repeat the conditional request.
4. Check whether the edge revalidated against the origin or answered from its stored copy without contacting it.
5. Verify that a changed etag at the origin produces a fresh answer at the edge rather than a not-modified built from stale state.
6. Record each conditional exchange with the validator used, the status and which layer answered it.

## Signals

- A conditional request returns not-modified while the origin's current content hash differs
- The etag reported by the edge never changes after an update made through the application
- A conditional request is answered from storage without a corresponding origin fetch in logs
- Weak and strong validators are mixed in a way that lets a changed body keep an old validator

## Patterns

**1. Exchange line**

```text
if-none-match: W/"abc" -> 304, status hit, origin fetch: none -> edge answered alone
after update: if-none-match: W/"abc" -> 200, status miss, new etag -> revalidated
```

**2. Validator compare**

```text
record origin etag and edge-reported etag per observation; a persistent mismatch marks stale revalidation state
```

**3. Layer attribution**

```text
304 with no origin fetch means the edge held the validator; a 304 accompanied by an origin fetch means the origin confirmed it
```

## Pitfalls

- Reading a 304 as proof the content is current when only the edge's stored copy was consulted
- Comparing validators across representations that were never meant to be the same resource
- Skipping the update step, which is the only way to see whether revalidation actually reaches the origin

## Done when

- Each conditional exchange records validator, status, cache token and origin involvement
- At least one exchange is repeated after a content update to confirm revalidation behaviour

## References

- [IETF RFC 9110 - Conditional requests](https://www.rfc-editor.org/rfc/rfc9110)
- [MDN - ETag header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/ETag)

Versions

The database has no other skills named conditional-request-behavior-audit.

Database snapshot: 13.11.2026 · package version ff787782cc74 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100br-etag-cache
    Add better-route 1.1 ETag and If-None-Match handling to GET or HEAD routes. Use for ETagMiddleware, strong or weak validators, custom etagResolver, WP_REST_Response preservation, comma-separated validators, wildcard matching, 304 responses, Cache-Control, proxy-stripped ETag…
  • 100etag-handler
    Manage etag handler operations. Auto-activating skill for API Development. Triggers on: etag handler, etag handler Part of the API Development skill category. Use when working with etag handler functionality. Trigger with phrases like "etag handler", "etag handler", "etag".
  • 100phy-http-cache-audit
    HTTP caching header analyzer that checks Cache-Control directives, ETag/Last-Modified freshness, Vary correctness, CDN cache status (X-Cache, CF-Cache-Status, Age), and stale-while-revalidate opportunities for any URL or local dev server. Identifies assets that should be cached…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.