• Recent
    • Tags
    • Popular
    • Register
    • Login

    Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

    Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website Mango 5 Documentation Website

    Anyone Using Pound load balancing

    User help
    3
    3
    988
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      Phillip Weeks
      last edited by

      Has anyone had success using Pound to filter between back end servers? We are using Pound to redirect users from common entry server to the appropriate back-end server based on the URl header. It works well and fast however some dashboards will not fully render and Pound complains headers: request URI too long. It appears the maxbuffer setting in Pound is too low and the request is being truncated. The fix requires re-configuring and recompiling the program with an increased maxbuffer param but as yet have not been able to get the fix working.

      1 Reply Last reply Reply Quote 0
      • MattFoxM
        MattFox
        last edited by MattFox

        @phillip-weeks said in Anyone Using Pound load balancing:

        Has anyone had success using Pound to filter between back end servers?

        Sorry no,
        I used mod_proxy with Apache for my configuration. Allowed me to use letsEncrypt SSL certs. Haven't had any major issues. Dunno if that would help accomplish what you're trying to do or you need Pound because it provides load balancing and the like...

        Good Luck

        Fox

        Edit: Found this little nugget of info that might help you with redirecting...

        A little further down the RewriteCond document:
        
        %{HTTP:header}, where header can be any HTTP MIME-header name
        
        So, you can do it, just not in quite the same form as the pre-extracted headers.
        
        Try this:
        
        RewriteCond %{HTTP:X-Forwarded-Port} !=443
        RewriteRule .* https://%{SERVER_NAME}%{REQUEST_URI} [R=301,L]
        

        Credit goes to shane madden on Server Fault

        Do not follow where the path may lead; go instead where there is no path.
        And leave a trail - Muriel Strode

        1 Reply Last reply Reply Quote 0
        • R
          rshah
          last edited by

          Nginx might also do what you want and may be simpler depending on how you set it up.

          You can also pretty easily adjust headers on Nginx (if needed)
          R

          1 Reply Last reply Reply Quote 0
          • First post
            Last post