oss/wallabag
oss/wallabag
1
0
Fork 0
mirror of https://github.com/wallabag/wallabag.git synced 2025-07-22 17:18:37 +00:00
Code Wiki Activity

Return 304 when content isn't reloaded using the API

Browse source 
Previously it was a 400 but this is more related to a real error.
Using the API user should only know the content got reloaded or not.
If reloaded: 200 otherwise: 304.
This commit is contained in:
Jeremy Benoist 2016-11-22 10:45:17 +01:00
parent 944b8d6175
commit 5cd0857e3c
No known key found for this signature in database
GPG key ID: BCA73962457ACC3C
2 changed files with 4 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

6
src/Wallabag/ApiBundle/Controller/EntryRestController.php
View file

@ -287,7 +287,7 @@ class EntryRestController extends WallabagRestController
/**
* Reload an entry.
* A response with HTTP Status 400 will be return if we weren't able to update the content (because it hasn't changed or we got an error).
* An empty response with HTTP Status 304 will be send if we weren't able to update the content (because it hasn't changed or we got an error).
*
* @ApiDoc(
* requirements={
@ -310,12 +310,12 @@ class EntryRestController extends WallabagRestController
'entry' => $entry,
]);
return new JsonResponse(['error' => 'Error while trying to fetch content'], 400);
return new JsonResponse([], 304);
}
// if refreshing entry failed, don't save it
if ($this->getParameter('wallabag_core.fetching_error_message') === $entry->getContent()) {
return new JsonResponse(['error' => 'Error while trying to extract content'], 400);
return new JsonResponse([], 304);
}
$em = $this->getDoctrine()->getManager();