Skip to content

fix: add X-Forwarded-For header requirement details for self-managed domains#1167

Open
erikbos-auth0 wants to merge 1 commit into
auth0:mainfrom
erikbos-auth0:fix-sm-proxy-xff-details
Open

fix: add X-Forwarded-For header requirement details for self-managed domains#1167
erikbos-auth0 wants to merge 1 commit into
auth0:mainfrom
erikbos-auth0:fix-sm-proxy-xff-details

Conversation

@erikbos-auth0
Copy link
Copy Markdown

Description

We should encourage customers using self-managed custom domain to set XFF header. Without that production functionality can be impacted and their proxy traffic might get rate limited.

References

Testing

Checklist

  • I've read and followed CONTRIBUTING.md.
  • I've tested the site build for this change locally.
  • I've made appropriate docs updates for any code or config changes.
  • I've coordinated with the Product Docs and/or Docs Management team about non-trivial changes.

@erikbos-auth0 erikbos-auth0 requested a review from a team as a code owner May 13, 2026 01:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant