You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Rupert Westenthaler (JIRA)" <ji...@apache.org> on 2015/07/06 10:18:04 UTC

[jira] [Resolved] (STANBOL-1432) ManagedSite returns 404 status on DELETE requests

     [ https://issues.apache.org/jira/browse/STANBOL-1432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rupert Westenthaler resolved STANBOL-1432.
------------------------------------------
    Resolution: Fixed

fixed with http://svn.apache.org/r1689331 in 0.12.1; merged with http://svn.apache.org/r1689332 to trunk

> ManagedSite returns 404 status on DELETE requests
> -------------------------------------------------
>
>                 Key: STANBOL-1432
>                 URL: https://issues.apache.org/jira/browse/STANBOL-1432
>             Project: Stanbol
>          Issue Type: Bug
>          Components: Entityhub
>    Affects Versions: 0.12.0
>            Reporter: Rupert Westenthaler
>            Assignee: Rupert Westenthaler
>             Fix For: 1.0.0, 0.12.1
>
>
> As reported by Adrian Dinu in [1] the ManagedSite returns 404 on a DELETE request for an existing Entity.
> A first investigation showed that the Entity is in fact deleted, but a 404 status is returned anyway.
> As a workaround users can check for a 404 response the content of the response.
> * If the content is empty the entity was deleted
> * If the content contains a message starting with {{No Entity with the parsed Id}} no entity with the requests ID was found.
> The fix will ensure that successful delete requests will return a 200 response code. In addition in case a single entity is deleted the response will return the data of the deleted entity.
> [1] http://markmail.org/message/f6vgxx44iukngizk



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)