All geek questions in one place

Listening for Incoming TCP Connections

It seems that all PAAS providers, including openshift, have

the service terminates the http / https traffic, looks at the Host header: then forwards the request to one listening port in your application.

I have the misfortune of having applications that need both an inbound HTTP listener and a raw TCP listener.

the proxies used by PAAS seem to support UPGRADE for websockets only (if that is).

Does anyone have any smart workarounds that I can use to deploy an application that needs to listen on two ports, one of which is not HTTP? or does anyone have a “real smart” job that allows me to get the same effect with one listening port?

+4
source share
1 answer

In the case of OpenShift Online, here is a FAQ that explains current port restrictions and some workarounds: https://www.openshift.com/kb/kb-e1038-i-cant-bind-to-a-port

OpenShift Online is also working to ensure that cartridge authors open their own ports in accordance with: https://www.openshift.com/content/at-least-one-port-for-external-use-excluding-8080-please

Let us know how this happens! https://www.openshift.com/forums/openshift

+1
source

Source: https://habr.com/ru/post/1489387/

More articles:


All Articles