Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ambivalent behaviour of wildcard pattern #122

Open
shreCoder opened this issue May 16, 2020 · 0 comments
Open

Ambivalent behaviour of wildcard pattern #122

shreCoder opened this issue May 16, 2020 · 0 comments

Comments

@shreCoder
Copy link

shreCoder commented May 16, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant