🤖 SSR Content v2

Server-Side Rendering via CloudFront Functions

🎯 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: 08:04:47 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 b53a4d0acd0fae2e5b27b3ef501aaf98.cloudfront.net (CloudFront)
x-amz-cf-id: SJvv539w5UWs5vMEK1icfCzIjzJQqvMPzNgebjke1FWCk6xQwQUFQg==
x-amzn-tls-cipher-suite: TLS_AES_128_GCM_SHA256
x-amzn-tls-version: TLSv1.3
x-amzn-trace-id: Self=1-69e9d29f-6ccba9e67f9068132f1742ef;Root=1-69e9d29f-4c17c96d132a12973cf19a8c
x-forwarded-for: 216.73.216.12
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