🎯 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:
04:49:22 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 4a49d4bbc62895d92884cc23c90b33fc.cloudfront.net (CloudFront)
x-amz-cf-id:
YYUjaNzSYRfGxGSoXW-tKhH2VzIRvslZ9-CkceR9bWhc0osUqOuBhg==
x-amzn-tls-cipher-suite:
TLS_AES_128_GCM_SHA256
x-amzn-tls-version:
TLSv1.3
x-amzn-trace-id:
Self=1-6a6d7ad1-1701c5570dd81cb5340c76bf;Root=1-6a6d7ad1-470ea3696a847c2c658f0cab
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