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.

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

Allow custom forwarded header #477

Closed
muhlemmer opened this issue Nov 9, 2023 · 2 comments · Fixed by #478
Closed

Allow custom forwarded header #477

muhlemmer opened this issue Nov 9, 2023 · 2 comments · Fixed by #478
Labels

Comments

@muhlemmer
Copy link
Collaborator

We have issues at zitadel to use the Forwarded header in production, because our hoster Vercel corrupts the header on the outgoing proxies request.

As a workaround we want to support also x-zitadel-forwarded in the same format as the current forwarded header.

@muhlemmer muhlemmer moved this to 🐛 Bugs/Small Issues in Product Management Nov 9, 2023
@livio-a
Copy link
Member

livio-a commented Nov 9, 2023

@eliobischof does this maybe also influece zitadel/zitadel#6891?

@github-project-automation github-project-automation bot moved this from 🐛 Bugs/Small Issues to ✅ Done in Product Management Nov 10, 2023
Copy link

🎉 This issue has been resolved in version 3.2.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants