use of external IP in HTTP Direct acceptor. - Forum - Technology Partner - Progress Community

use of external IP in HTTP Direct acceptor.

 Forum

use of external IP in HTTP Direct acceptor.

  • Hi,

          I need to understand the use of External URL while configuring HTTP direct acceptor.

          I need to have multiple HTTP direct acceptors  with same port.

          Client would always send  HTTP request  on HTTP port 80. I have several services , each one is mapped to one acceptor. I can't make more than one acceptor with same port.So i need to understand if external IP would be useful.

         would really appreciate for your help.

         thanks in advance. 

    Girdhar

  • egirdhar wrote:


          I need to understand the use of External URL while configuring HTTP direct acceptor.

    External URL is for the case of a Proxy Server or some form of DNS lookup where the local machine (hosting the broker) is unaware of the URL that an external client would have to use in order to reach the host/port.   There are cases where the broker has to advertise the URL to clients or remote brokers (particularly for cases such as HTTP Tunneling with load-balancing or failover).  Normally, the machine can lookup its own host name, but when there is a proxy server, this is not possible. 

    But you can administratively override the local lookup with the information about what the 'real URL' is by using this property.

    It will not solve your problem of having multiple acceptors using the same port.  That is not possible -- each acceptor has to have a unique port.

  • Each acceptor can have multiple protocols associated with it, e.g. you can have:

    http://host:80/service1

    http://host:80/service2

    http://host:80/service3

    ...

    That should avoid the need for multiple acceptors