Jersey itself has no notion of sessions. Whatever authentication
provider you are using would probably handle this out in front of
Jersey.
If you're rolling your own: "401 - Unauthorized" is appropriate. That
will direct most clients to re-initiate authentication if possible
(Digest, for instance).
On Wed, Apr 27, 2011 at 10:57 AM, Arthur Yeo <artyyeo_at_gmail.com> wrote:
> Looks like when it does expires, it has the same effects as making the
> session.invalidate() call.
>
> On Tue, Apr 26, 2011 at 11:18 PM, Rob - <skyscrapper666_at_hotmail.com> wrote:
>>
>> Is there such a thing? I don't think there is a HTTP error code dealing
>> with server side session. REST is stateless anyways.
>>
>> ________________________________
>> Date: Tue, 26 Apr 2011 10:29:24 -0700
>> From: artyyeo_at_gmail.com
>> To: users_at_jersey.java.net
>> Subject: [Jersey] HTTP status code for Sess Expiration
>>
>> All,
>> What's the HTTP status code returned to the browser when a session expires
>> in Jersey?
>> --
>> Arthur Y.
>
>
>
> --
> Arthur Y.
>
--
Gary Moore
http://www.gmoore.net