AWS AmazonCloudFront documentation change
Summary
Added documentation about configuring CloudFront to forward WebSocket headers in addition to existing HTTP headers.
Security assessment
The change adds functionality documentation about WebSocket headers but does not introduce or address any security-specific features or concerns.
Diff
diff --git a/AmazonCloudFront/latest/DeveloperGuide/adding-cloudfront-headers.md index d17232562..5a9f51309 100644 --- a/AmazonCloudFront/latest/DeveloperGuide/adding-cloudfront-headers.md +++ b/AmazonCloudFront/latest/DeveloperGuide/adding-cloudfront-headers.md @@ -9 +9 @@ Device type headersViewer location headersHeaders to determine the viewer's head -You can configure CloudFront to add specific HTTP headers to the requests that CloudFront receives from viewers and forwards on to your origin or [edge function](./edge-functions.html). The values of these HTTP headers are based on characteristics of the viewer or the viewer request. The headers provide information about the viewer's device type, IP address, geographic location, request protocol (HTTP or HTTPS), HTTP version, TLS connection details, [JA3 fingerprint](https://github.com/salesforce/ja3), and JA4 fingerprint. +You can configure CloudFront to add specific HTTP headers to the requests that CloudFront receives from viewers and forwards on to your origin or [edge function](./edge-functions.html). The values of these HTTP headers are based on characteristics of the viewer or the viewer request. The headers provide information about the viewer's device type, IP address, geographic location, request protocol (HTTP or HTTPS), HTTP version, TLS connection details, [JA3 fingerprint](https://github.com/salesforce/ja3), and JA4 fingerprint. You can also configure your distribution's cache behavior to forward WebSocket headers. For more information, see [Use WebSockets with CloudFront distributions](./distribution-working-with.websockets.html).