This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Thank you for raising this request! We appreciate your feedback and queries
After reviewing the behavior and the relevant specifications, we’ve concluded that we will not introduce fallback handling when an invalid
X-Forwarded-Protovalue is provided. While it would be technically possible to attempt to infer the protocol, doing so would introduce security risks and could result in incorrect request handling in certain configurations.From a security and correctness standpoint, Liberty follows a fail-explicit approach. If a forwarded protocol header is present but invalid, the safest behavior is to treat this as a configuration error rather than attempting to guess the intended protocol. Guessing or silently correcting the value could mask misconfigurations upstream and, in some cases, lead to unintended security implications.
The recommended approach is to ensure that the proxy or front-end server is configured to send a valid and accurate
X-Forwarded-Protovalue that reflects the actual client connection. Correcting the configuration at that level ensures predictable behavior and avoids ambiguity in request processing.We understand this may require changes in your proxy or server setup, but this approach aligns with best practices and helps maintain secure and reliable request handling.
Please let us know if you would like assistance validating your current setup or have further questions.
Looking forward to more ideas from you