🎯 Routing Decision
🤖 Lambda Origin (SSR v2)
Bot/crawler detected → Server-rendered content from Lambda Function URL
📊 Request Information
Content Source:
AWS Lambda (v2)
CDN:
CloudFront
Router:
CloudFront Functions
Rendering:
Server-Side
User-Agent:
Amazon CloudFront...
Rendered At:
18:58:05 UTC
🔍 All Request Headers
accept-encoding:
br,gzip
cf_bot:
true
content-length:
0
host:
kgbyvupn7cdf5ef3ybhbn6wqlm0oasyf.lambda-url.us-east-1.on.aws
user-agent:
Amazon CloudFront
via:
2.0 08cfd09b74c4fdf0b487a291e1267ba2.cloudfront.net (CloudFront)
x-amz-cf-id:
90rM1uiBXE8_P3ZuqXTTUuvG8NXEyTUUGdJQFkjNybtbxJDQpdX8IA==
x-amzn-tls-cipher-suite:
TLS_AES_128_GCM_SHA256
x-amzn-tls-version:
TLSv1.3
x-amzn-trace-id:
Self=1-6a42c03c-74d91f5e35593d5c0d019743;Root=1-6a42c03c-6c82cef35ab9e5fb1a251191
x-forwarded-for:
216.73.217.64
x-forwarded-port:
443
x-forwarded-proto:
https
📋 How This Request Was Handled (v2)
1
Bot requests https://ssr-poc-2.spribe-sandbox1.click
2
CloudFront receives request at edge location
3
CloudFront Function (viewer-request) analyzes User-Agent
4
Decision: Bot/crawler detected
5
cf.selectRequestOriginById('Lambda-SSR-Origin-V2')
6
CloudFront routes to Lambda Function URL origin
7
Lambda renders HTML with SEO metadata
8
SEO-optimized content delivered to bot