🪨Headers received at origin

Every HTTP header the origin saw after the edge ran

These are the HTTP headers your origin received. If a Header Management rule added one, it's in this list. If a Custom Origin Header rule rewrote the Host, the value below reflects that rewrite. Don't trust DevTools — trust this.
Headers received by the origin 26 shown · 6 infra hidden · show all
accept
*/*
accept-encoding
gzip, br, zstd, deflate
cloudfront-forwarded-proto
https
cloudfront-is-android-viewer
false
cloudfront-is-desktop-viewer
true
cloudfront-is-ios-viewer
false
cloudfront-is-mobile-viewer
false
cloudfront-is-smarttv-viewer
false
cloudfront-is-tablet-viewer
false
cloudfront-viewer-address
216.73.216.99:19732
cloudfront-viewer-asn
16509
cloudfront-viewer-city
Columbus
cloudfront-viewer-country
US
cloudfront-viewer-country-name
United States
cloudfront-viewer-country-region
OH
cloudfront-viewer-country-region-name
Ohio
cloudfront-viewer-http-version
2.0
cloudfront-viewer-latitude
39.96250
cloudfront-viewer-longitude
-83.00610
cloudfront-viewer-metro-code
535
cloudfront-viewer-postal-code
43215
cloudfront-viewer-time-zone
America/New_York
cloudfront-viewer-tls
TLSv1.3:TLS_AES_128_GCM_SHA256:fullHandshake
host
ew5y1l0189.execute-api.us-east-1.amazonaws.com
user-agent
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
via
2.0 74cca41adcf2dc7ddd618c2457dd4778.cloudfront.net (CloudFront)
What to look for
Header Management
Custom headers your rule added appear above with the values you configured.
Custom Origin Header
The host value reflects any hostname your rule set for the origin request.
x-gcdn-*
Internal GraniteCDN signal headers — if you see any, they're ones the origin-request Lambda deliberately left in.