gateway-workers
Build and Review Cloudflare Gateway Workers
Gateway Forward integrations require entrypoints, context handling, and continuation rules that differ from ordinary Workers. This skill guides implementation and validation using current Cloudflare references.
Mit meinem Agent installieren
Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.
Review the Skillstore skill "gateway-workers" from https://skillstore.io/skills/cloudflare-gateway-workers.md and its manifest at https://skillstore.io/api/skills/cloudflare-gateway-workers/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.
Agent-lesbare Ressourcen
Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.
Testen
„gateway-workers“ wird verwendet. Review a Worker that only implements a default fetch handler.
Erwartetes Ergebnis:
- The default handler does not implement the Gateway Forward contract.
- Export GatewayMiddleware extending WorkerEntrypoint and implement its handle method.
- Validate the named RPC entrypoint and a permitted request through a scoped Forward policy.
„gateway-workers“ wird verwendet. Review a Worker that changes the destination and calls next() twice.
Erwartetes Ergebnis:
- Call next() at most once; it always targets the original destination.
- Destination URL and host changes do not redirect continuation.
- A separate fetch() subrequest does not inherit the user Gateway policies or egress configuration.
„gateway-workers“ wird verwendet. Review a Worker that trusts identity headers and buffers all response bodies.
Erwartetes Ergebnis:
- Use Gateway-provided identity instead of client-supplied identity headers.
- Handle rejected identity lookups separately from anonymous identity values.
- Stream response bodies and omit bodies for HEAD requests and statuses 204, 205, and 304.
Sicherheitsaudit
SicherAll 20 static findings are false positives involving Markdown formatting, documentation links, API terminology, or related-skill references. The skill explains independent subrequest risks and recommends trusted identity, scoped validation, and streaming. No evidence found of prompt injection, credential extraction, malicious execution, or unauthorized data transfer.
Risikofaktoren
⚙️ Externe Befehle (7)
🌐 Netzwerkzugriff (9)
📁 Dateisystemzugriff (3)
Diesen Bericht teilen & zitieren
Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.
Berichtslink kopieren
https://skillstore.io/skills/cloudflare-gateway-workers/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown-Badge
[](https://skillstore.io/skills/cloudflare-gateway-workers?utm_source=security_passport_badge)HTML-Badge
<a href="https://skillstore.io/skills/cloudflare-gateway-workers?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cloudflare-gateway-workers/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Einbettungskarte
<iframe src="https://skillstore.io/embed/skills/cloudflare-gateway-workers.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Wissenschaftliche Zitate (APA · BibTeX · CFF)
APA-Zitat
cloudflare. (2026). gateway-workers security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cloudflare-gateway-workers/audits/1BibTeX-Zitat
@techreport{cloudflare-cloudflare-gateway-workers-2026,
author = {cloudflare},
title = {gateway-workers security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/cloudflare-gateway-workers/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "gateway-workers security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "cloudflare"
date-released: "2026-10-25"
url: "https://skillstore.io/skills/cloudflare-gateway-workers/audits/1"
identifiers:
- type: other
value: "skillstore:cloudflare-gateway-workers:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore-Score
Warum dieser Score Evidenzvertrauen: MittelWas Sie erstellen können
Implement Gateway middleware
Adapt an existing Worker to the named RPC entrypoint and correct continuation contract.
Review identity-dependent behavior
Check identity trust, posture lookups, missing values, and lookup failures before introducing identity-dependent decisions.
Validate a scoped rollout
Plan Gateway integration checks covering policy matching, supported traffic, response handling, and streaming.
Diese Prompts ausprobieren
Explain how GatewayMiddleware differs from a default fetch handler, using the current Forward guide.
Review my Worker for zero-or-one next() calls, synthetic responses, and independent fetch() subrequests. Explain any policy inheritance implications.
Review my Gateway identity and posture handling. Distinguish anonymous users, absent posture values, and rejected lookups. Recommend explicit failure behavior.
Create a scoped Gateway test plan for this Worker. Cover RPC entrypoints, continuation, inspection order, streaming, response restrictions, and traffic limitations.
Bewährte Praktiken
- Consult current Forward documentation and type-check against installed Gateway types before implementation.
- Use Gateway identity and explicitly handle missing context values and rejected lookups.
- Test the named RPC entrypoint and a scoped Gateway path, including continuation and streaming behavior.
Vermeiden
- Treating a successful direct fetch-handler request as proof that Gateway integration works.
- Using next() to redirect, retry, fan out, or continue more than once.
- Assuming independent fetch() subrequests inherit Gateway policies or egress configuration.
Häufig gestellte Fragen
Does a default fetch handler implement Gateway Forward?
Can next() redirect a request to another destination?
Do independent fetch() subrequests inherit Gateway policies?
How should identity lookup failures be handled?
Which traffic limitations should I check?
Does this skill deploy or test a Worker automatically?
Entwicklerdetails
Autor
cloudflareLizenz
MIT
Skillstore-Revision
r1
Versionshinweis
Der Autor hat keine Version angegeben.
Ref.
0596e7dcb24514e7373fb1c8c2a058e2990a6e83
Aktualität der Wartung
25.10.2026
Nutzung
0 Downloads · 0 Aufrufe
Dateistruktur
📄 SKILL.md