Cloudfront not adding response headers from Cloudfront functions when requests are made in HTTP/3
When HTTP/3 is enabled in Cloudfront, response headers added in Cloudfront functions (like the CORS headers shown in this example and the security headers in this example) are not actually added. However, these headers are added as usual when the requests are made in HTTP/2. Headers set with 'Response headers policy' in Cloudfront behaviors are also properly added.
Is it a bug or am I missing out on something?
Edit: Attach some screenshots for my configuration:
- Newest
- Most votes
- Most comments
I've just tested this and had no issues with at least access-control-allow-origin being added when HTTP/3 is in use. This was the case when using both CloudFront Functions as well as Response Header Policies.
Please check that your function uses all lowercase for the header key names.
It may also be worth trying a different browser.
Relevant content
- Accepted Answerasked 2 years ago
- asked 25 days ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Thank you for your response. Yes, the function is using all lowercase for the header key names. I've updated my question with some screenshots to show my configuration. In addition to curl shown in the screenshots, I've also tried the latest version of Firefox and Chrome, and the problem persists across the browsers.
I suggest you raise a case with AWS support to investigate further. Please provide them the x-amz-cf-id response headers for each of your examples above. You could also try removing and re-adding the cloudfront function association to see if that resolves the problem.