Yes, HEAD can be used to obtain meta-information about the entity. Hence
agree with Rukshan's suggestion.
On Wed, Jan 24, 2018 at 4:28 PM, Praminda Jayawardana
wrote:
> I think you can do something like following. here GET /books resource
>> should return all the books in the
>
> I think you can do something like following. here GET /books resource
> should return all the books in the system and HEAD /books resource can
> return some metadata of the system. Similar way you can check the
> connectivity of the system.
>
> HEAD /books
>
Since what you need is a health
On Sat, Jan 20, 2018 at 9:25 AM, Rukshan Premathunga
wrote:
> Hi Nishadi,
>
> In APIM you cannot grantee the behavior when you have conflict resources.
> Also i don't think your rest implementation is comply with restful service.
>
> GET /books/{book-id}
>
> GET
On Sat, Jan 20, 2018 at 9:25 AM, Rukshan Premathunga
wrote:
> Hi Nishadi,
>
> In APIM you cannot grantee the behavior when you have conflict resources.
> Also i don't think your rest implementation is comply with restful service.
>
> GET /books/{book-id}
>
> GET
Hi Nishadi,
In APIM you cannot grantee the behavior when you have conflict resources.
Also i don't think your rest implementation is comply with restful service.
GET /books/{book-id}
GET /books/healthcheck
After the path/books it should represent book's id or something. So we
cannot have a sub
Hi Nishadi,
Since this model has the conflict as you have mentioned, IMO I think it
would be better to use a query parameter for the book-id instead of using
the path parameter.
Cheers,
*Nadeeshaan Gunasinghe*
Senior Software Engineer, WSO2 Inc. http://wso2.com
+94770596754 | nadeesh...@wso2.com
Hi all,
I have several REST APIs that need to be exposed via API Manager 2.1.0. For
example, I have a micro service that manages books and in that micro
service the following two APIs need to be exposed via the API manager.
- GET /books/{book-id}
- Retrieve the information of a