1983-01...@gmx.net wrote:
I have no usecase for this at the moment :-(, I only provide patches
for
stuff I suffer from at work.
The below looks like a use case to me.
As this [1] draft lays out Negotiate and Kerberos may apply to
connection or request level auth. We are just lucky that the
Hi,
several authentication mechanisms require a session (*not* HTTP session)
or connection being initiated when authentication is performed and
principal cached for subsquent requests [1], [2].
Now, I want to patch our SPNEGO authenticator in Tomcat 6 to behave
stateful. I once contributed
On 27/10/2012 14:50, Michael-O wrote:
Hi,
several authentication mechanisms require a session (*not* HTTP session)
or connection being initiated when authentication is performed and
principal cached for subsquent requests [1], [2].
Now, I want to patch our SPNEGO authenticator in Tomcat 6
Am 2012-10-27 16:57, schrieb Mark Thomas:
On 27/10/2012 14:50, Michael-O wrote:
Hi,
several authentication mechanisms require a session (*not* HTTP session)
or connection being initiated when authentication is performed and
principal cached for subsquent requests [1], [2].
Now, I want to
On 27/10/2012 16:28, Michael-O wrote:
Am 2012-10-27 16:57, schrieb Mark Thomas:
The only mechanism to maintain state between HTTP requests is the HTTP
session. You might be able to hack something together (in a non-portable
way) on a per connection basis but that is likely to require some
Am 2012-10-27 18:38, schrieb Mark Thomas:
On 27/10/2012 16:28, Michael-O wrote:
Am 2012-10-27 16:57, schrieb Mark Thomas:
The only mechanism to maintain state between HTTP requests is the HTTP
session. You might be able to hack something together (in a non-portable
way) on a per connection
On 27/10/2012 17:56, Michael-O wrote:
Am 2012-10-27 18:38, schrieb Mark Thomas:
On 27/10/2012 16:28, Michael-O wrote:
Am 2012-10-27 16:57, schrieb Mark Thomas:
The only mechanism to maintain state between HTTP requests is the HTTP
session. You might be able to hack something together (in a
Am 2012-10-27 19:25, schrieb Mark Thomas:
Is this something worth being filed in Bugzilla as a longterm goal for
Tomcat 8?
Sure, but without a proposed patch I suspect it will sit there for a few
years and then closed as WONTFIX. With a patch, it still might not get
fixed but at least you'll
On 27/10/2012 18:57, Michael-O wrote:
Am 2012-10-27 19:25, schrieb Mark Thomas:
Is this something worth being filed in Bugzilla as a longterm goal for
Tomcat 8?
Sure, but without a proposed patch I suspect it will sit there for a few
years and then closed as WONTFIX. With a patch, it still
Am 2012-10-27 20:22, schrieb Mark Thomas:
On 27/10/2012 18:57, Michael-O wrote:
Am 2012-10-27 19:25, schrieb Mark Thomas:
Is this something worth being filed in Bugzilla as a longterm goal for
Tomcat 8?
Sure, but without a proposed patch I suspect it will sit there for a few
years and then
Yes W8 is here but HPQ is still plummeting. Get rid of your CEO and get someone
who can improve your stock price!
Date: Sat, 27 Oct 2012 19:57:30 +0200
From: 1983-01...@gmx.net
To: users@tomcat.apache.org
Subject: Re: Detect in an authenticator whether a connection is persistent or
not
On Sat, Oct 27, 2012 at 11:36 AM, ken dias kend...@hotmail.com wrote:
Yes W8 is here but HPQ is still plummeting. Get rid of your CEO and get
someone who can improve your stock price!
Que?
--
Hassan Schroeder hassan.schroe...@gmail.com
On 27/10/2012 19:32, Michael-O wrote:
Am 2012-10-27 20:22, schrieb Mark Thomas:
On 27/10/2012 18:57, Michael-O wrote:
Am 2012-10-27 19:25, schrieb Mark Thomas:
Is this something worth being filed in Bugzilla as a longterm goal for
Tomcat 8?
Sure, but without a proposed patch I suspect it
I have no usecase for this at the moment :-(, I only provide patches
for
stuff I suffer from at work.
The below looks like a use case to me.
As this [1] draft lays out Negotiate and Kerberos may apply to
connection or request level auth. We are just lucky that the first
14 matches
Mail list logo
