IBM Sterling Ideas
formerly Watson Supply Chain
Submit new product ideas for Watson Supply Chain solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain
Connect with IBM experts and your peers on the
Supply Chain Collaboration Community and the Order Management Interest Group
Submit ideas for other Watson Customer Engagement Products:
• Watson Marketing
• Watson Campaign Automation
• Watson Commerce
Currently IBM SP when configured as a HTTP Reverse Proxy, does not pass the HTTP host header from the client's request to the backend application. The request here is to have this a configurable option, similar to Apache's ProxyPreserveHost option.
How will this idea be used?
As a customer of cloud service, I will be access it using the public URL and the request passes through IBM SP to the backend service. The service might have some logic based on how the client accessed it (assuming there are multiple URL's with which they can access the same service), for ex: There could be an email that needs to be sent which has the same URL as how the client accessed the service. In such cases, since SP does not preserve the HTTP host header, the URL in the emails will have the service's internal hostname and the end user will not be able to click on the link and access the service.
|What is your industry?||Financial Markets|
|What is the idea priority?||Urgent|
|Link to original RFE|