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

Resolver - Does path parameter supports regex now? #561

Closed
jeevanrd opened this issue Sep 23, 2015 · 3 comments
Closed

Resolver - Does path parameter supports regex now? #561

jeevanrd opened this issue Sep 23, 2015 · 3 comments

Comments

@jeevanrd
Copy link

I saw one of your comments in #282 saying, it's on your todo task lists. would be glad to know the updates on it

Currently when I create a endpoint with path having "/abcd/[0-9]/" it throws error saying "path must only contain alphanumeric and '. -, _, ~, /' characters".

I realized after digging into resolver code that you are already doing regex based path matching using ngx.re.match function. I hope if you remove the alphanumeric condition in (dao/schemas/apis.lua), it should work straight away right?

@thibaultcha
Copy link
Member

See #369. Support of multiple path and host will give support for regex a sense. We have not decided when to start working on it. The issue is to implement an easy to use prioritisation system between multiple paths, which is easy in text configuration in nginx, but no so much when dealing with a REST API.

@jeevanrd
Copy link
Author

@thibaultcha any rough idea on timelines because we are kind of needed this feature.

@thibaultcha
Copy link
Member

No, no rough idea of when this will be implemented for now, sorry. Closing it as this was a question and #369 is the proper issue.

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

3 participants