Skip to content

Ambivalent behaviour of wildcard pattern #122

Open
@shreCoder

Description

@shreCoder

When I tried to route a specific pattern Im facing ambiguous behaviour which conflicts with wildcard pattern

I tried these patterns;

case 1: /*/tz/tm/paid
case 2: /*/tz/tm/checked

it is interpreting as wildcard pattern " /* ".

log is showing :

key : "JLRoutePattern"
value : /*

When just tested by changing the wildcard pattern to // it is working.

key : "JLRoutePattern"
value : /*/tz/tm/checked

Sample urls:

1. https://www.mysite.com/tz/tm/checked

2. https://www.mysite.com/tz/tm/paid

how can we achieve this by giving support to both these patterns

case 1: /*/tz/tm/paid
case 2: /*/tz/tm/checked

Can someone from the contributors can help or share the insights. Thanks in advance.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions