cxf-users mailing list archives

Hi Sergey,
sorry that should have read:
"when I hit a URL that is NOT registered to a service/media type
that I get a 500 back"
...which kind of changes the meaning a little bit.
What I mean is that if i hit a URL where there is no service
registered then I get a 500. I mentioned media type just to cover the
fact that if you have a service registered at a URL but you specify a
bad media type you (correctly) get the same result.
I was just wondering from a general interest point of view really, I
don't especially have an issue with how it currently is. Besides I'm
too lazy to read the spec and I know you have :-).
Brad.
On Fri, Jul 18, 2008 at 2:13 PM, Sergey Beryozkin
<sergey.beryozkin@iona.com> wrote:
> Hi
>> Hi,
>>
>> I've noticed that when I hit a URL that is registered to a
>> service/media type that I get a 500 back.
>
> Can you clarify a bit more please and post a sample URL ? Are you saying
> that when Accept contains a media type for which no providers/methid match
> has been found then 500 is returned or are you referring to something else ?
>
>> Just wondering if maybe it
>> would be better for the server to return a 404 in these cases?.
>
> There're few grey areas in the code as far as the proper status code
> reporting is concerned, I've added it to the TODO list in the JAX-RS docs.
> 500 code is the eaisiest one to return in case of failurs/exceptions :-) -
> it does not require one to properly read HTTP 1.1 spec and/or JAX-RS
> specification :-).
>
> It all will be tightened in the months to come, I believe for a number of
> cases a proper response or error codes are returned now, for ex, when 'null'
> is returned, and in few other cases.
>
> Cheers, Sergey
>>
>> Cheers,
>> Brad.
>
> ----------------------------
> IONA Technologies PLC (registered in Ireland)
> Registered Number: 171387
> Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
>