Petals BC REST

Path matching on request (consumes) takes the last match instead of first

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.0.1-BC
  • Fix Version/s: 1.1.0-BC
  • Component/s: Consumer mode
  • Security Level: Public
  • Description:
    Hide

    When a request URL matches multiple paths mapping defined in a consume, instead of taking the first one into account, it takes the last one (and uselessly process all of the matching paths).

    It would be more intuitive to take the first one into account.

    Show
    When a request URL matches multiple paths mapping defined in a consume, instead of taking the first one into account, it takes the last one (and uselessly process all of the matching paths). It would be more intuitive to take the first one into account.
  • Environment:
    -

People

Dates

  • Created:
    Mon, 9 Jan 2017 - 14:50:32 +0100
    Updated:
    Mon, 9 Jan 2017 - 16:25:16 +0100
    Resolved:
    Mon, 9 Jan 2017 - 16:25:16 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.