conditional-request-behavior-audit
/conditional-request-behavior-audit
Sprawdza, jak własny pośrednik obsługuje walidatory etag i last-modified, by wykryć serwowanie nieaktualnych danych po zmianie u źródła.
- Autor
- Wsh7Ash ↗
- Repozytorium
- edgescout ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 28.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 2
Brak sygnałów. Repozytorium zmienione 28.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Sprawdza, jak własny pośrednik obsługuje walidatory etag i last-modified, by wykryć serwowanie nieaktualnych danych po zmianie u źródła.
Oryginalny opis (EN)
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
Jak działa
- Procedure
- Signals
- Patterns
- Pitfalls
- Done when
- References
Podgląd SKILL.md
--- 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)
Wersje
W bazie nie ma innych skilli o nazwie conditional-request-behavior-audit.
Migawka bazy z 13.11.2026 · wersja paczki ff787782cc74 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100br-etag-cache
Dodaje obsługę ETag i If-None-Match do tras GET i HEAD w better-route, w tym odpowiedzi 304, Cache-Control i izolację w CachingMiddleware. - 100etag-handler
Prawdopodobnie pomaga obsługiwać nagłówki ETag w API, na przykład przy żądaniach warunkowych i cache'owaniu. - 100phy-http-cache-audit
Analizuje nagłówki cache HTTP dla dowolnego adresu URL lub lokalnego serwera: Cache-Control, ETag, Last-Modified, Vary, status cache CDN oraz możliwości stale-while-revalidate.