Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    HA Proxy - change backend based on URL not working (for me)

    Scheduled Pinned Locked Moved Cache/Proxy
    4 Posts 2 Posters 677 Views
    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.
    • C
      crester
      last edited by

      Hello.
      Let's see if someone can help me.
      As the subject, I have 2 backends I want to use based on the URL
      First is host matches:
      Second is same host but I want to test an URL parameter to use another backend.
      787022b1-61b0-42d1-90bb-158b374a963a-image.png

      This is the configuration and actions are:
      77d80ffe-5bfb-493b-8ec2-a75f18c0f6af-image.png

      I am becoming crazy, because it doesn't work in any parameter, trying every parameter and changing the criteria.

      Does someone see what is happening?
      Some light will illuminate my soul (and let me go to have a saturday walk)

      Thank you.
      KR

      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @crester
        last edited by

        @crester
        The ACL looks somewhat odd.
        You did state a parameter name. Without a parameter name an URL parameter ACL might be quite useless.
        And you have "Not" checked. So the matching is inverted.

        1 Reply Last reply Reply Quote 0
        • C
          crester
          last edited by

          @viragomann Thank you for your tips.
          I have been testing few things (even removing the unseen "NOT") and it still does't work for me
          i.e just a simple rule to detect the origin IP and redirect to a backend doesn't work in my side

          Thank you

          V 1 Reply Last reply Reply Quote 0
          • V
            viragomann @crester
            last edited by

            @crester
            The Not is subordinate in this ACL.
            You have configured an ACL to match an URL parameter. Is this really what you want at all? Since you didn't state any parameter name, I'm not sure in this.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.