Request Journey

A visual trace: DNS → CloudFront → API Gateway → Lambda

Reached Lambda • 200 OK

How your browser got here

Open this page from your custom domain to see the full chain in action.

DNS lookup (CNAME)

You typed c8botofbh1.execute-api.us-east-1.amazonaws.com. Your device asked DNS: “Where does this name point?” If you set a CNAME in GoDaddy, DNS answered with the CloudFront hostname.

Host: c8botofbh1.execute-api.us-east-1.amazonaws.com Type: CNAME Answer: dxxxx.cloudfront.net

CloudFront (edge)

Your request hit the nearest CloudFront edge location. CloudFront terminated HTTPS (TLS) using your ACM certificate and then forwarded the request to your API origin.

TLS: ✅ Caching: (API usually disabled) Header: Via: 2.0 738fb660a52e749e6f8b6a3cd561b080.cloudfront.net (CloudFront)

API Gateway (REST API)

CloudFront called API Gateway using its execute-api endpoint. API Gateway matched your route and invoked your Lambda integration.

Route: GET / Stage: test

Lambda (this code)

Lambda executed your Python handler and returned HTML with Content-Type: text/html. Your browser rendered it as a web page.

AWS Request ID: 542eec76-dcc0-4b8a-b6a2-b206404e9ed7 UTC: 2026-08-01 11:23:43 UTC

Note: Some headers (like Via or CloudFront viewer headers) may not appear depending on your CloudFront policy and whether you’re calling the CloudFront domain directly vs your custom domain.

What Lambda sees (live)

URL (inferred)

https://c8botofbh1.execute-api.us-east-1.amazonaws.com/

Client IP (from X-Forwarded-For)

216.73.217.47

User-Agent

Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)

Query string

{}

Try it

Refresh to replay the animation

Ctrl/Cmd + R

If you want to hide /test stage

Set CloudFront origin path to /test

Status

Lambda reached

✅ Yes (HTTP 200)

Time (UTC)

2026-08-01 11:23:43 UTC