Hi Sanjeewa,
Thanks for the clarification.
If we consider REST best practices usually we do use above URL pattern to
> get resource when we know resource ID.
>
>
We have changed the API according to the suggestions and added the search
to already available resource in the micro service.
On Tue, Aug 30, 2016 at 12:52 PM, Shan Mahanama wrote:
> Hi all,
>
> We are designing an API for search. We need to pass a regex as the search
> query.
>
> Sample API - /search/{query}
>
If we consider REST best practices usually we do use above URL pattern to
get resource when
Hi all,
We are designing an API for search. We need to pass a regex as the search
query.
Sample API - /search/{query}
Query - wso2.*
URL Encoded Request - /search/wso2.%2A
When we encode the regex and call the API, we get the following error
message.
No matching resource found in the API for