1 Answer
- Newest
- Most votes
- Most comments
1
Kindly note that CloudFront is currently not supporting HTTP/2 towards origins. The connection from CloudFront back to your origin server is still made using HTTP/1.1:
New – HTTP/2 Support for Amazon CloudFront - https://aws.amazon.com/blogs/aws/new-http2-support-for-cloudfront/ HTTP version - https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/RequestAndResponseBehaviorCustomOrigin.html#RequestCustomHTTPVersion
answered 2 years ago
Relevant content
- asked 2 years ago
- Accepted Answerasked a year ago
- Accepted Answerasked 3 years ago
- asked 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Ohh, okk.
Hence was debugging an issue wherein our ttfb(time to first byte) is high when cloudfront is used compared to serving from alb directly.I asked a separate question here
If cloudfront supports http2 to origin, I think it helps a lot given cloudfront is at edge locations and a new connection to the origin server for most of the viewer requests increases latency.