🎯 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:
16:49:21 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 51acaa499b8a860796a06c2570d22afe.cloudfront.net (CloudFront)
x-amz-cf-id:
Q61tUM3xN38AKm4s1l1sB4xnz7I3Oztt0jSosEhrageOAcmbuEzgOQ==
x-amzn-tls-cipher-suite:
TLS_AES_128_GCM_SHA256
x-amzn-tls-version:
TLSv1.3
x-amzn-trace-id:
Self=1-6a6f7511-499fa43652ee271b525c6ac3;Root=1-6a6f7511-18c8b2d3217b524e71e0e7e1
x-forwarded-for:
216.73.216.238
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