aboutsummaryrefslogtreecommitdiffhomepage
path: root/application/api
Commit message (Collapse)AuthorAgeFilesLines
* API: Get History endpointArthurHoaro2017-05-071-0/+71
| | | | See http://shaarli.github.io/api-documentation/#links-history-get
* API: add DELETE endpointArthurHoaro2017-05-071-0/+23
| | | | | | Based on #840 See http://shaarli.github.io/api-documentation/\#links-link-delete
* REST API: implement PUT methodArthurHoaro2017-05-072-0/+68
| | | | | * Related to #609 * Documentation: http://shaarli.github.io/api-documentation/#links-link-put
* REST API: implement POST link serviceArthurHoaro2017-03-273-3/+86
|
* application: introduce the Shaarli\Config namespaceVirtualTam2017-03-041-1/+1
| | | | | | | | | | | Namespaces have been introduced with the REST API, and should be generalized to the whole codebase to manage object scope and benefit from autoloading. See: - https://secure.php.net/manual/en/language.namespaces.php - http://www.php-fig.org/psr/psr-4/ Signed-off-by: VirtualTam <virtualtam@flibidi.net>
* REST API: implements getLink by ID serviceArthurHoaro2017-02-192-2/+55
| | | | See http://shaarli.github.io/api-documentation/#links-link-get
* REST API - getLinks: support the visibility parameterArthurHoaro2017-01-171-3/+2
|
* Update LinkFilter to be able to filter only public linksArthurHoaro2017-01-161-1/+2
| | | | | | No update regarding the UI or the API for now Fixes #758
* Merge pull request #727 from ArthurHoaro/api/getlinksArthurHoaro2017-01-152-0/+117
|\ | | | | REST API: implement getLinks service
| * REST API: implement getLinks serviceArthurHoaro2017-01-152-0/+117
| | | | | | | | See http://shaarli.github.io/api-documentation/#links-links-collection-get
* | API: expect JWT in the Authorization headerVirtualTam2017-01-151-3/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Relates to https://github.com/shaarli/Shaarli/pull/731 Added: - require the presence of the 'Authorization' header Changed: - use the HTTP Bearer Token authorization schema See: - https://jwt.io/introduction/#how-do-json-web-tokens-work- - https://tools.ietf.org/html/rfc6750 - http://security.stackexchange.com/q/108662 Signed-off-by: VirtualTam <virtualtam@flibidi.net>
* | API: fix JWT signature verificationVirtualTam2017-01-041-7/+5
|/ | | | | | | | | | | | | | | | | | | | | | Fixes https://github.com/shaarli/Shaarli/issues/737 Added: - Base64Url utilities Fixed: - use URL-safe Base64 encoding/decoding functions - use byte representations for HMAC digests - all JWT parts are Base64Url-encoded See: - https://en.wikipedia.org/wiki/JSON_Web_Token - https://tools.ietf.org/html/rfc7519 - https://scotch.io/tutorials/the-anatomy-of-a-json-web-token - https://jwt.io/introduction/ - https://en.wikipedia.org/wiki/Base64#URL_applications - https://secure.php.net/manual/en/function.base64-encode.php#103849 Signed-off-by: VirtualTam <virtualtam@flibidi.net>
* REST API structure using Slim frameworkArthurHoaro2016-12-158-0/+428
* REST API routes are handle by Slim. * Every API controller go through ApiMiddleware which handles security. * First service implemented `/info`, for tests purpose.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-17 13:23:37 +0000