[jboss-jira] [JBoss JIRA] (WFCORE-185) Api returns internal server error instead of not found for non-existing path

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013019#comment-13013019 ] 

Brian Stansberry commented on WFCORE-185:
-----------------------------------------

A 404 is fine for missing resources when GET is used, since the resource address as part of the Request-URI; agreed that it's not good for a POST.

What's the benefit of "Management attribute not found" and "Management operation not found"?  I can see a custom response code or header for "Management resource not found" since 404 is inappropriate for POST and what resources are available changes over time. But if the resource address is valid, the set of attributes and operations exposed by a resource is not something that is changing around a lot. So I don't see the value for a client of such a code/header over simply reading the failure details from the response body.

> Api returns internal server error instead of not found for non-existing path
> ----------------------------------------------------------------------------
>
>                 Key: WFCORE-185
>                 URL: https://issues.jboss.org/browse/WFCORE-185
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Heiko Rupp
>            Assignee: Brian Stansberry
>              Labels: rhq
>             Fix For: 1.0.0.Beta1
>
>
> When I try to e.g. /subsystem=foo:read-resource the api returns a 500 internal server error.
> In http-land, the return code for "not found" is normally 404.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)