Amplify is not passing headers on custom domains

[uspai]

Before opening, please confirm:

• I have checked to see if my question is addressed in the FAQ.
• I have searched for duplicate or closed issues.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id

demy2iltb613o

Region

us-east-2

Amplify Console feature

Custom headers

Describe the bug

Hi,
I have a reverse proxy from /api/<> to https://prod.linvo.io/<>
For some reason, it's not passing my custom headers.
I have 3 custom domains registered:
beta.linvo.io
dashboard.linvo.io
managers.linvo.io

Trying to access https://*.linvo.io/api/managers/self

Now here is the funny thing,
If I am using the provided domain, it works!
https://master.demy2iltb613o.amplifyapp.com/api/managers/self

The reverse proxy worked for the last 2 months.
This morning I woke up and it's failing.
This is a production version and honestly, I am not sure what to do.

Expected behavior

Proxy pass works like before without failing.

Reproduction steps

Register here:
https://managers.linvo.io/register

Login, and you will see the error.
https://managers.linvo.io/login

You can copy the request, change the domain to
https://master.demy2iltb613o.amplifyapp.com

And it will work.

Build Settings

version: 1
frontend:
  phases:
    preBuild:
      commands:
        - npm install
    build:
      commands:
        - npm run managers
  artifacts:
    baseDirectory: build
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

Additional information

It was working for the last 2 months!

[github-actions]

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!

[behrooziAWS]

It looks like you've made some changes since when you cut this issue. Namely, you are no longer hosting the custom domain on amplify and instead you own the distribution and are setting the amplify app as the origin. Are you still having issues? What were the header names that stopped being sent to the reverse proxy?

[uspai]

Hi behrooziAWS, it was a production version I had to do changes.
I am using now CloudFront, with some URL rewriting (it's not a good solution).
Did you see anything in your side?

[calavera]

Custom headers are added to responses for custom domains as expected already. Closing this issue since it has been resolved.

[github-actions]

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]

This issue has been automatically locked.