Cloudflare Tunnel: docs imply top-level originRequest.access applies to all ingress rules, but cloudflared silently ignores it

Aperta
  • Qualcosa non va?
#32,006 1 commento 0 reazioni 2 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@nikitacano ci sta già lavorando.

Dal 10/7/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

product:cloudflare-one stale

Which pages are affected?

What is wrong?

The "Origin configuration" section teaches that a top-level originRequest block sets defaults for all ingress rules, and the access parameter page says to "add the following rule to originRequest" without qualifying where. Following the two pages together, a reasonable reading is that this protects every service behind the tunnel:

originRequest:
  access:
    required: true
    teamName: <team>
    audTag:
      - <aud>

ingress:
  - hostname: app.example.com
    service: http://localhost:8000
  - service: http_status:404

In reality cloudflared silently ignores a top-level access block. The config validates, no warning is logged, and unauthenticated traffic is forwarded to the origin. The JWT validation middleware is only attached when the access block sits under an individual ingress rule: validateIngress in ingress/ingress.go reads the raw per-rule r.OriginRequest.Access, not the merged defaults (the merge in ingress/config.go copies the top-level block, but its result is never consulted for middleware attachment).

Verified on cloudflared 2026.7.1 with an A/B test against the same hostname (no Access app on the hostname, so no JWT on any request): top-level block returned 200 from the origin; the identical block moved under the ingress rule returned 403 from cloudflared.

This is a known cloudflared behaviour: cloudflare/cloudflared#784 (open since 2022) reports it, and a maintainer described it as "largely intended" because Access rules are tied to hostnames. The docs have not been updated to match, which matters because the failure mode is a security control that users believe is active but is not (see also the last comment on that issue).

Suggested fix

  1. In the configuration-file partial's "Origin configuration" section, note that access is an exception to top-level inheritance and must be set on each ingress rule.
  2. In the origin-parameters partial's access section, state explicitly that the block must be placed under originRequest of each individual ingress rule, and that a top-level block is not enforced.
Lingua principale
MDX
Stelle
5.4k
Fork
17.3k
Merge medio
1g 19h
PR unite (30g)
528

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cloudflare/cloudflare-docs

Tutte le issue di cloudflare/cloudflare-docs

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.