Grouper Users - Open Discussion List

[Alexander Dutton <>]

Hi Chris,

That header matches the /*/responseMetadata/resultCode in the response
body (an 'F' if any of the deletions failed).

I've fiddled with my client implementation to happily accept 500s as
well as 200s.

All the best,

Alex

On 29/09/15 12:27, Chris Hyzer wrote:
> I agree with you but I lost that battle I believe.  I think you should 
> ignore the status code and just look at the X-Grouper-success: HTTP header, 
> that was a T right?  If not, send me the full request and response and let 
> me take a look.  Partial successes are a little tricky
>
> Thanks,
> Chris
>
> -----Original Message-----
> From: 
> 
>  
> [mailto:]
>  On Behalf Of Alexander Dutton
> Sent: Tuesday, September 29, 2015 5:32 AM
> To: 
> 
> Subject: [grouper-users] Web Services return 500, but have mostly done what 
> I want
>
> Hi all,
>
> I'm playing with the web services, and just tried deleting a list of
> groups. My user doesn't have enough privileges over all of them, so I
> was expecting some to be denied.
>
> The HTTP response has come back with a status code of  500 Internal
> Server Error, yet has a fully-formed response body, including a message
> that says "There were 17 successes and 1 failures of deleting groups.".
>
> I would have expected to only have seen a 500 when something has
> actually gone wrong server side, and probably a 200 in this case.¹
>
> I suspect there are other instances of this in the REST API, but haven't
> checked. Would it make sense to harmonise on 200 when nothing has
> actually gone unexpectedly wrong?
>
> Best regards,
>
> Alex
>
>
> ¹ There's also a 207 Multi-Status code that could be used to indicate a
> partial success, but that's a bit too WebDAV specific.
>

-- 
Alexander Dutton
Linked Open Data Architect; data.ox.ac.uk, OxPoints
Data and Information Architecture, IT Services