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).
Shape the future of IBM!
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:
Search existing ideas
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
we do have many applications on a vast number of network interfaces (if/eth) per unix host. In case we need fail-over, we assign multiple ports per application (e.g. 8000, 8001 for application 'a' and 8002 for application 'b').
The same port(s) might be used for other applications on another interface. This way we can select applications by IP/Port or hostname/port.
However, we also use IHS as a reverse proxy in front of Liberty Profile.
In fact, we only need to bind IHS publicly to use the application.
So we asked our unix department how we could bind Liberty to loopback addresses instead.
While we would need multiple local (loopback) IPs to match the outgoing IPs (due to port reuse on other interfaces), they asked us if unix sockets were a valid option as well.
Hence I am asking for Unix file socket support for both IHS and Liberty to avoid binding to a public interface and creating more loopback/127.x.x.x interfaces.
I am not even sure HTTP over unix file sockets is even possible and feasible.
Do not place IBM confidential, company confidential, or personal information into any field.