On Tue, Feb 14, 2006 at 11:11:22AM -0700, Brad Nicholes wrote:
On 2/14/2006 at 3:50 am, in message
[EMAIL PROTECTED],
[EMAIL PROTECTED] wrote:
On Mon, Feb 13, 2006 at 03:42:27PM -0700, Brad Nicholes wrote:
The other problem that I see in the configuration is that the
Location
On 2/17/2006 at 10:38:17 am, in message
[EMAIL PROTECTED],
[EMAIL PROTECTED] wrote:
On Tue, Feb 14, 2006 at 11:11:22AM -0700, Brad Nicholes wrote:
On 2/14/2006 at 3:50 am, in message
[EMAIL PROTECTED],
[EMAIL PROTECTED] wrote:
On Mon, Feb 13, 2006 at 03:42:27PM -0700, Brad Nicholes wrote:
On Mon, Feb 13, 2006 at 03:42:27PM -0700, Brad Nicholes wrote:
On 2/13/2006 at 8:39:41 am, in message
[EMAIL PROTECTED],
[EMAIL PROTECTED] wrote:
On Mon, Feb 13, 2006 at 08:26:39AM -0700, Brad Nicholes wrote:
Yes, we do need to make this change. With the provider based
rearchitecting
On 2/14/2006 at 3:50 am, in message
[EMAIL PROTECTED],
[EMAIL PROTECTED] wrote:
On Mon, Feb 13, 2006 at 03:42:27PM -0700, Brad Nicholes wrote:
The other problem that I see in the configuration is that the
Location
/authany defines an authtype and authname but no authentication
provider.
On 2/10/2006 at 5:58:43 pm, in message
[EMAIL PROTECTED],
[EMAIL PROTECTED] wrote:
Joshua Slive wrote:
On 1/26/06, Ian Holsman [EMAIL PROTECTED] wrote:
Hi Joshua:
httpd.conf.in has the new structure
httpd-std.conf (the one I was looking at) didn't ;(
Hmmm... httpd-std.conf doesn't exist
On Mon, Feb 13, 2006 at 08:26:39AM -0700, Brad Nicholes wrote:
Yes, we do need to make this change. With the provider based
rearchitecting of authentication in httpd 2.2, this left authorization
in an unpredictable state especially when using multiple authorization
types. You were never
On 2/13/2006 at 8:39:41 am, in message
[EMAIL PROTECTED],
[EMAIL PROTECTED] wrote:
On Mon, Feb 13, 2006 at 08:26:39AM -0700, Brad Nicholes wrote:
Yes, we do need to make this change. With the provider based
rearchitecting of authentication in httpd 2.2, this left
authorization
in an
On 2/13/2006 at 8:39:41 am, in message
[EMAIL PROTECTED],
[EMAIL PROTECTED] wrote:
On Mon, Feb 13, 2006 at 08:26:39AM -0700, Brad Nicholes wrote:
Yes, we do need to make this change. With the provider based
rearchitecting of authentication in httpd 2.2, this left
authorization
in an
Joshua Slive wrote:
On 2/10/06, David Reid [EMAIL PROTECTED] wrote:
Joshua Slive wrote:
On 1/26/06, Ian Holsman [EMAIL PROTECTED] wrote:
Hi Joshua:
httpd.conf.in has the new structure
httpd-std.conf (the one I was looking at) didn't ;(
Hmmm... httpd-std.conf doesn't exist in trunk.
Just
Joshua Slive wrote:
On 1/26/06, Ian Holsman [EMAIL PROTECTED] wrote:
Hi Joshua:
httpd.conf.in has the new structure
httpd-std.conf (the one I was looking at) didn't ;(
Hmmm... httpd-std.conf doesn't exist in trunk.
Just ran into this and couldn't quite believe what I was seeing.
I have
On 2/10/06, David Reid [EMAIL PROTECTED] wrote:
Joshua Slive wrote:
On 1/26/06, Ian Holsman [EMAIL PROTECTED] wrote:
Hi Joshua:
httpd.conf.in has the new structure
httpd-std.conf (the one I was looking at) didn't ;(
Hmmm... httpd-std.conf doesn't exist in trunk.
Just ran into
On 1/26/06, Ian Holsman [EMAIL PROTECTED] wrote:
Hi Joshua:
httpd.conf.in has the new structure
httpd-std.conf (the one I was looking at) didn't ;(
Hmmm... httpd-std.conf doesn't exist in trunk.
Joshua.
I haven't done any of this work myself, but...
On 1/26/06, Ian Holsman [EMAIL PROTECTED] wrote:
Hi.
It looks like recently some people have changed how authorization is
working on the trunk.
Could those people please
1. add a note to docs/upgrading.html to document what us idiots need to
Hi Joshua:
httpd.conf.in has the new structure
httpd-std.conf (the one I was looking at) didn't ;(
regards
Hi.
It looks like recently some people have changed how authorization is
working on the trunk.
Could those people please
1. add a note to docs/upgrading.html to document what us idiots need to
do to get our config to work again?
2. change httpd-std.conf so it doesn't reference the
15 matches
Mail list logo