users@tyrus.java.net

Re: Returning 404 rather than 101 when /resource name/ doesn't exist

From: Pavel Bucek <pavel.bucek_at_oracle.com>
Date: Mon, 13 May 2013 13:36:34 +0200

Hi Gerard,

there is nothing like JAX-RS filters. I don't think there is a way how
to return custom status. There is some feature request filed against the
spec - https://java.net/jira/browse/WEBSOCKET_SPEC-199, so you might
want to vote for that issue or add your comment there..

surely we can do something like it in implementation specific way, feel
free to file RFE against tyrus

Thanks,
Pavel

On 5/2/13 5:53 PM, Gerard Davison wrote:
> Hi,
>
> I section 4.3 of the JSR 356 spec there is an example of using a @PathParam to map part of the path to a parameter, although I note there isn't an @QueryParam to match, but as per RFC 6455 4.2.2. it should be possible to return a 404 status code without initiating a WebSocket interchange.
>
> I can't find an obvious code path to do this as presumable onOpen is too late as a message has already been send down the connection. Is there a -RS like request filter available so we can intercept this?
>
> Thanks,
>
> Gerard