HTTP Listener sending to 443 not specificed port number

Question

We are doing an implementation where we need to recieve data to a HTTP listener endpoint but the third party has said they can only send to a URL and default the port to 443.

What is the best approach to work around this without encountering issues for future projects as this third party always used 443 which does not work with multiple customer channel/zones

Answer 1

Since only one channel at a time can use a given port, and you have the possibility of needing this third party to connect to multiple channels/zones, and the third party is unable to use a custom port, you'll need to utilize a reverse proxy or load balancer in front of QIE.

The reverse proxy will be listening on port 443 with SSL enabled and accept connections from the third party system.  It will then route those messages to QIE, using the port that QIE is listening on (i.e. port 20001)

Comments

Thank you for the response. From a scaling perspective, is there any plans to support the ability to bind to paths and not just http listeners?

---

There are no specific plans at this time, but one thing to note is you could set up a channel in QIE that is listening on port 443 with the sole purpose of routing messages to other channels.  This would effectively bring the reverse proxy functionality into QIE, negating the need for an external system.