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.
Установить с помощью моего Агента
Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.
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.Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.
Ресурсы для AI-агентов
Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.
Протестировать
Использование «gateway-workers». Review a Worker that only implements a default fetch handler.
Ожидаемый результат:
- 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». Review a Worker that changes the destination and calls next() twice.
Ожидаемый результат:
- 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». Review a Worker that trusts identity headers and buffers all response bodies.
Ожидаемый результат:
- 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.
Аудит безопасности
БезопасноAll 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.
Факторы риска
⚙️ Внешние команды (7)
🌐 Доступ к сети (9)
📁 Доступ к файловой системе (3)
Поделиться и цитировать этот отчет
Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.
Копировать ссылку на отчёт
https://skillstore.io/skills/cloudflare-gateway-workers/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportЗначок Markdown
[](https://skillstore.io/skills/cloudflare-gateway-workers?utm_source=security_passport_badge)Значок HTML
<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>Встраиваемая карточка
<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>Академические ссылки (APA · BibTeX · CFF)
Цитата APA
cloudflare. (2026). gateway-workers security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cloudflare-gateway-workers/audits/1Цитата BibTeX
@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
Почему такая оценка Достоверность доказательств: СреднийЧто вы можете построить
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.
Попробуйте эти промпты
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.
Лучшие практики
- 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.
Избегать
- 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.
Часто задаваемые вопросы
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?
Сведения для разработчиков
Автор
cloudflareЛицензия
MIT
Ревизия Skillstore
r1
Примечание о версии
Автор не указал версию.
Репозиторий
https://github.com/cloudflare/skills/tree/86505e44f87d801aa1864a3c4109e9a8ae5c409f/skills/gateway-workersСсылка
0596e7dcb24514e7373fb1c8c2a058e2990a6e83
Актуальность поддержки
25.10.2026
Использование
0 загрузок · 0 просмотров
Структура файлов
📄 SKILL.md