#dominoforever | Product Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Allow X-Forwarded-For with port

When Domino is behind some Microsoft proxies, e.g. in Azure App Service, the X-Forwarded-For header contains port information and actually results in an error 400 Reason: Request cannot be processed, request contains an invalid HTTP header.

sample:

X-FORWARDED-FOR: 125.33.57.15:23222


It would be good to have this scenario working - I think it was working fine with v11.


I've opened a support case CS0315075 for this, but as I was able to find a workaround with additional nginx proxy, I've closed it.


  • Guest
  • May 14 2022
  • Needs Review
  • Attach files