Return-Path: X-Original-To: apmail-shiro-user-archive@www.apache.org Delivered-To: apmail-shiro-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 719A310BD8 for ; Fri, 14 Feb 2014 08:01:20 +0000 (UTC) Received: (qmail 49456 invoked by uid 500); 14 Feb 2014 08:01:19 -0000 Delivered-To: apmail-shiro-user-archive@shiro.apache.org Received: (qmail 49384 invoked by uid 500); 14 Feb 2014 08:01:16 -0000 Mailing-List: contact user-help@shiro.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@shiro.apache.org Delivered-To: mailing list user@shiro.apache.org Received: (qmail 49376 invoked by uid 99); 14 Feb 2014 08:01:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Feb 2014 08:01:15 +0000 X-ASF-Spam-Status: No, hits=1.3 required=5.0 tests=SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Feb 2014 08:01:11 +0000 Received: from jim.nabble.com ([192.168.236.80]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1WEDhZ-0001nQ-8S for user@shiro.apache.org; Fri, 14 Feb 2014 00:00:49 -0800 Date: Fri, 14 Feb 2014 00:00:49 -0800 (PST) From: versatec To: user@shiro.apache.org Message-ID: <1392364849252-7579648.post@n2.nabble.com> In-Reply-To: References: Subject: Re: Why is JSESSIONID on any URL? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org I did the tracking-mode thing in web.xml, too, and I see the same behavior. Yet, neither do I have an explanation for it. glassfish 4.0 javax.servlet-api, 3.1.0 Mojarra 2.2.5 shiro 1.2.2 Grizzly Framework 2.3.1 WELD 2.0.0 (SP1) -- View this message in context: http://shiro-user.582556.n2.nabble.com/Why-is-JSESSIONID-on-any-URL-tp7579643p7579648.html Sent from the Shiro User mailing list archive at Nabble.com.