Re: ERR_CONNECTION_TIMED_OUT


Amit Kumar Gupta
 

Upcoming support for TCP routing (not just HTTP routing) will allow you to
run a container that serves HTTPS traffic.

Currently the wso2 product ships with an untrusted self-signed cert. How
do you plan on using wso2? Will it be exposed to external consumers, or is
it just something internal that other applications need to talk to? If
exposed to external consumers, will you want to configure it with a real
trusted cert? What about DNS, would it be exposed under a proper DNS
hostname (instead of clients requesting a raw IP)? Do you plan on being
able to horizontally scale your wso2 application, i.e. run more than one
instance of the server to share traffic load and provide fault tolerance?

Cheers,
Amit

On Thu, Mar 3, 2016 at 8:39 PM, Nanduni Nimalsiri <nandunibw(a)gmail.com>
wrote:

Hi Eric,

Thank you very much for looking into this matter. Actually I was not well
and I couldn't reply you. I am really really grateful for you and Amit for
looking into this matter very generously.

Actually, your description explains me well. The problem here is that WSO2
products use HTTPS, and there's no way to change that behavior because that
will be affecting the overall company process.

WSO2 products are based on Carbon platform and they are run with HTTPS
mode. [1] is a basic WSO2 product repo which runs the WSO2 ESB.
[1] https://github.com/wso2/product-esb

So, can you propose me any other way to deploy WSO2 products in Cloud
Foundry, if I'm unable to handle with Docker images. As a company, we are
now in the strategy of trying out our products in different PaaSes. So your
support is highly appreciated.

Best regards,
Nanduni.

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.