multiple web services on same port

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf multiple web services on same port

  • Creator
    Topic
  • #55472
    David Barr
    Participant

      Is it possible to run multiple web services on the same port with Cloverleaf?

      I’d like to be able to handle different types of requests with different URLs, and I’d also like to have different authentication based on the URL. I’m not sure the best way to handle this. I could use one inbound thread for the requests, and set up TRXIDs to route to different outbound threads based on the URL, but that doesn’t address the authentication.

      The main reason that I want to do this is I want to set up rules on our organization’s load balancer to forward requests for a subdomain to Cloverleaf, and I’d rather not have to request load balancer changes every time we set up a new interface

      Another option would be to set up Apache on the Cloverleaf server as a reverse proxy and forward requests to different ports based on the URL that Apache receives. I could probably also let Apache handle the authentication step.

    Viewing 2 reply threads
    • Author
      Replies
      • #85438
        Jerry Tilsley
        Participant

          This is possbile and you can route based on the URL portion at the end.  I haven’t done a lot of this, mainly just in sample scenarios, but I do know that it works.

          Jerry

        • #85439
          David Barr
          Participant

            How do you do that? How do you handle different credentials for different routes?

            Our current plan is to use Cisco Netscaler to forward all requests to a certain subdomain to one port on the Cloverleaf server. We’re running HAProxy on Cloverleaf which will terminate the SSL session and pass to a different port on the localhost address based on the requested URL. We would have a separate Cloverleaf thread listening on a different port for each interface.

          • #85440
            Jerry Tilsley
            Participant

              For a client:

              You can define a single conneciton with single soap/rest client with a URL like http://myhost:13000, then you can set the Cloverleaf TrxId Determination to PATH so that each url branch like http://myyhost:13000/branch1 and http://myhost:13000/branch2 can be routed differently.

              OR

              You can define a single connection with multiple soap/rest clients with each having a path to the same or different servers and/or ports, then you can name each of those clients to a name you like, by default they get a name like MySOAPDispatch.

          Viewing 2 reply threads
          • The forum ‘Cloverleaf’ is closed to new topics and replies.