Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-5146

Backend path take precedence over my Routing rule

    XMLWordPrintable

Details

    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Hide
      1. create a product
      2. set a backend path: /echo, upstream: echo.3scale.net
      3. set Rourting policy. The mapping rule is this: 
         {
     "url": "http://example.com",
     "condition": {
         "combine_op": "and",
         "operations": [
             {
                 "op": "==",
                 "value": "bar",
                 "value_type": "plain",
                 "match": "query_arg",
                 "query_arg_name": "foo"
             }
         ]
     }
 }
      4. send a request to /echo?foo=bar

      Expected result: the request is routed to example.com
      Actual result: the request is routed to echo.3scale.net

      Show
      create a product set a backend path: /echo, upstream: echo.3scale.net set Rourting policy. The mapping rule is this: { "url" : "http: //example.com" , "condition" : { "combine_op" : "and" , "operations" : [ { "op" : "==" , "value" : "bar" , "value_type" : "plain" , "match" : "query_arg" , "query_arg_name" : "foo" } ] } } send a request to /echo?foo=bar Expected result: the request is routed to example.com Actual result: the request is routed to echo.3scale.net

    Description

      When I set a Routing policy that checks a query parameter, I expected the rule takes precedence over my backends, but backend rule wins.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. THREESCALE-4016 APIAP + second routing policy breaks apicast

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              Unassigned Unassigned
              rhn-support-tkonishi Takayuki Konishi
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: