Re: Release of mod_python 3.3.

2006-12-07 Thread Graham Dumpleton
On 07/12/2006, at 9:14 PM, Graham Dumpleton wrote: Once that is decided I'll roll the tarball, likely tonight. I assume we'll use release-3-3-0b as the tag? Based on past conventions, that tag seems appropriate. If all is okay do we then just retag as 3.0.1? Hmmm, I think you know

Re: Release of mod_python 3.3.

2006-12-07 Thread Jim Gallacher
Graham Dumpleton wrote: On 07/12/2006, at 12:42 AM, Jim Gallacher wrote: Graham Dumpleton wrote: There were no more comments on basic apache.import_module() documentation so I have tweaked a few last things, committed it and marked as resolved the final issue in JIRA tagged for 3.3. Thus,

Re: vote on concept of ServerTokens Off

2006-12-07 Thread Jeff Trawick
On 12/6/06, Colm MacCarthaigh [EMAIL PROTECTED] wrote: On Wed, Dec 06, 2006 at 01:43:49PM -0500, Jeff Trawick wrote: * The Apache HTTP Server project believes that most people who want to avoid sending the Server header mistakenly think that doing so may protect their server from attacks

Re: vote on concept of ServerTokens Off

2006-12-07 Thread Jeff Trawick
On 12/6/06, Henrik Nordstrom [EMAIL PROTECTED] wrote: ons 2006-12-06 klockan 09:38 -0500 skrev Jeff Trawick: Why other than ego do we want to make it hard to disable this output? Technical reason: Not advertising the brand and version makes it very hard for clients (user-agents and proxies)

Re: vote on concept of ServerTokens Off

2006-12-07 Thread Mathieu CARBONNEAUX
Hi, what the difference with no header and Header = Server: Apache without version with prod args of servertoken... if is to hide apache version only there no need to modify ServerToken directive... if is to hide apache completly ok...it's other problem... but a security level i'm not sure

Re: vote on concept of ServerTokens Off

2006-12-07 Thread Maxime Petazzoni
-0 here. I don't see the point of earning 20 bytes per request when you can save many more with mod_deflate or tidying the output. It's not the job of the webserver. I won't veto it since you might find a use to this feature if it is implemented, but it's like you also want to let admins

Re: Creating a thread safe module and the problem of calling of 'CRYPTO_set_locking_callback' twice!

2006-12-07 Thread Darryl Miles
Frank wrote: Joe Orton wrote: On Wed, Dec 06, 2006 at 06:20:55PM +, Darryl Miles wrote: [...] Is there an API to get the current value ? Yes, CRYPTO_get_locking_callback/CRYPTO_get_id_callback. [...] I already know that this functions exists. But what if my module gets inited before

Re: Creating a thread safe module and the problem of calling of 'CRYPTO_set_locking_callback' twice!

2006-12-07 Thread William A. Rowe, Jr.
Frank wrote: Joe Orton wrote: Yes, CRYPTO_get_locking_callback/CRYPTO_get_id_callback. [...] I already know that this functions exists. But what if my module gets inited before mod_ssl, which doesn't use the get-functions to determine that something is already there? I was in the hope to

Clarification on example provided

2006-12-07 Thread Martin Stoufer
Graham, After pouring over the comments sent by you and Jim regarding my session/class examples, I have a better feel for what is expected in good coding models. Could you make some clarifications on one of the examples you provided: class SessionEnabled: def __init__(self, target):

Re: Clarification on example provided

2006-12-07 Thread Graham Dumpleton
Martin Stoufer wrote .. Graham, After pouring over the comments sent by you and Jim regarding my session/class examples, I have a better feel for what is expected in good coding models. Could you make some clarifications on one of the examples you provided: class SessionEnabled:

DBD spewing crit error messages on OS X default install (trunk)

2006-12-07 Thread Roy T. Fielding
This is a bit unsettling, especially since I neither need nor want any database-backed auth. == [Thu Dec 07 13:49:44 2006] [notice] Digest: generating secret for digest authent ication ... [Thu Dec 07 13:49:44 2006] [notice] Digest: done [Thu Dec 07 13:49:44 2006] [crit] (70023)This

Re: Clarification on example provided

2006-12-07 Thread Martin Stoufer
Graham Dumpleton wrote: Martin Stoufer wrote .. Graham, After pouring over the comments sent by you and Jim regarding my session/class examples, I have a better feel for what is expected in good coding models. Could you make some clarifications on one of the examples you provided:

Re: DBD spewing crit error messages on OS X default install (trunk)

2006-12-07 Thread Sander Temme
On Dec 7, 2006, at 2:12 PM, Roy T. Fielding wrote: This is a bit unsettling, especially since I neither need nor want any database-backed auth. That brings up two issues: 1) should this module be in most, and 2) Yes we might consider turning down those log messages a bit If the module

Re: DBD spewing crit error messages on OS X default install (trunk)

2006-12-07 Thread Nick Kew
On Thu, 7 Dec 2006 14:54:57 -0800 Sander Temme [EMAIL PROTECTED] wrote: On Dec 7, 2006, at 2:12 PM, Roy T. Fielding wrote: This is a bit unsettling, especially since I neither need nor want any database-backed auth. That brings up two issues: 1) should this module be in most, and

Re: Wrong etag sent with mod_deflate

2006-12-07 Thread Henrik Nordstrom
tor 2006-12-07 klockan 02:31 +0100 skrev Justin Erenkrantz: mod_deflate should just add the W/ prefix if it's not already there. -- justin No, that won't work. You still be just as non-conforming by doing that. But if mod_deflate may to produce different octet-level results on different

Re: Wrong etag sent with mod_deflate

2006-12-07 Thread Henrik Nordstrom
tor 2006-12-07 klockan 02:42 +0100 skrev Justin Erenkrantz: -1 on adding semantic junk to the existing ETag (and keeping it strong); that's blatantly uncool. Any generated ETag from mod_deflate should either be the original strong version or a weak version of any previous etag. mod_deflate

Re: walk caching to avoid extra authnz

2006-12-07 Thread Chris Darroch
Hi -- William A. Rowe, Jr. wrote: It so happens I'm starting one of those cycles again right now with the changes to the mis-handling of file matches that Nick(?) corrected in trunk, and I'll study your patch in tandem. Thanks for your work!!! Much appreciated, but alas, Justin pointed