Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

user-agent header in request getting replaced by "Amazon Cloudfront" #1992

Closed
vinay-aryan opened this issue Jun 24, 2021 · 8 comments
Closed

user-agent header in request getting replaced by "Amazon Cloudfront" #1992

vinay-aryan opened this issue Jun 24, 2021 · 8 comments
Labels
archived This issue has been locked. hosting question Further information is requested

Comments

@vinay-aryan
Copy link

my application is not receiving actual user-agent value of customer device it's getting replace by "Amazon Cloudfront". we don't have any setting that can change this cloudfront configuration
@github-actions
Copy link

Hi 👋, thanks for opening! While we look into this...

If this issue is related to custom domains, be sure to check the custom domains troubleshooting guide to see if that helps. Also, there is a more general troubleshooting FAQ that may be helpful for other questions.

Lastly, please make sure you've specified the App ID and Region in the issue!

@Jay2113 Jay2113 added question Further information is requested hosting labels Jul 14, 2023
@p00000001
Copy link

p00000001 commented Jul 30, 2023 •
edited
Loading

I'm also experiencing this problem. My Next.js app in AWS Amplify has important functionality using the user-agent header but the value is always "Amazon Cloudfront".

I see this issue is over 2 years old. Is there now a way we can keep the original user-agent header in Amplify or access the Cloudfront configuration for our AWS Amplify apps? Or if it's problematic to play with the user-agent then adding an additional header like origin-user-agent would work fine for us - just some way to access the original user agent.

@p00000001
Copy link

@Jay2113 - could you advise if there is any current solution to this issue or plans to fix it? As it's preventing us from deploying our app on AWS. Many thanks.

@p00000001
Copy link

@vinay-aryan Were you ever able to find a solution to this issue? Thanks!

@p00000001 p00000001 mentioned this issue Sep 13, 2023
Closed
5 tasks
@kaito-hao
Copy link

Hello Amplify team, good to see this is in progress. Could you please kindly provide an ETA? We are rolling out a feature blocked by this. Thank you.

@mauerbac
Copy link
Member

This feature is now supported with our latest launch!

Check out the details here: https://aws.amazon.com/blogs/mobile/cdn-caching-improvements-for-better-app-performance-with-aws-amplify-hosting/

@github-actions GitHub Actions
Copy link

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

@github-actions GitHub Actions
Copy link

This issue has been automatically locked.

@github-actions github-actions bot added the archived This issue has been locked. label Aug 13, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Aug 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
archived This issue has been locked. hosting question Further information is requested
Projects
Amplify Hosting Feature Request Tracker - 2024
Status: Done
Milestone
No milestone
Development

No branches or pull requests
5 participants
@mauerbac @vinay-aryan @Jay2113 @p00000001 @kaito-hao