Re: translate_name and/or map_to_storage hooks

Sam Carleton wrote: On 3/27/07, Sam Carleton [EMAIL PROTECTED] wrote: On 3/27/07, Issac Goldstand [EMAIL PROTECTED] wrote: More importantly, lets say my module is called mod_coolapp and when I have it installed, you get to it at /coolapp. I want /coolapp to be the equivalent to the

Re: translate_name and/or map_to_storage hooks

Sam Carleton wrote: On 4/4/07, Sam Carleton [EMAIL PROTECTED] wrote: On 3/27/07, Sam Carleton [EMAIL PROTECTED] wrote: On 3/27/07, Issac Goldstand [EMAIL PROTECTED] wrote: More importantly, lets say my module is called mod_coolapp and when I have it installed, you get to it at

one module per task

On 4/6/07, Nick Kew [EMAIL PROTECTED] wrote: A good starting point is one module per task. How many tasks does your application comprise? How many of those tasks can be accomplished using existing modules? I like the concept on one module one task, but I want to try to keep everything in one

Redundant SSL virtual host warnings?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Virtual hosts and SSL don't mix. Or so people say, for the simple reason that in order to reach the HTTP negotiation an SSL connection must be established first with a certificate/key pair. If you give it a try, Apache fills its log with the SSL

Re: Chunked transfer encoding on responses.

lör 2007-04-07 klockan 04:00 -0500 skrev William A. Rowe, Jr.: Of course this person is entirely wrong if the client doesn't Accept-Encoding: chunked which is exactly the logic we test. So why is there a dependency on keep-alive being enabled? Regards Henrik signature.asc Description:

Re: Chunked transfer encoding on responses.

On 4/8/07, Henrik Nordstrom [EMAIL PROTECTED] wrote: So why is there a dependency on keep-alive being enabled? If keep-alive is disabled for the connection, then Connection: Close tends to be more efficient anyway... -- justin

Re: Redundant SSL virtual host warnings?

sön 2007-04-08 klockan 18:48 +0100 skrev Jay L. T. Cornwall: So the part I'm leading up to is: how about a way to turn off these warnings? Or perhaps a simple certificate analysis to see if the wildcard matches all the virtual hosts for which it serves? Sounds good to me. Related to this,

Re: Redundant SSL virtual host warnings?

On Apr 8, 2007, at 11:24 AM, Henrik Nordstrom wrote: sön 2007-04-08 klockan 18:48 +0100 skrev Jay L. T. Cornwall: So the part I'm leading up to is: how about a way to turn off these warnings? Or perhaps a simple certificate analysis to see if the wildcard matches all the virtual hosts for

Re: Redundant SSL virtual host warnings?

On 04/08/2007 08:24 PM, Henrik Nordstrom wrote: sön 2007-04-08 klockan 18:48 +0100 skrev Jay L. T. Cornwall: So the part I'm leading up to is: how about a way to turn off these warnings? Or perhaps a simple certificate analysis to see if the wildcard matches all the virtual hosts for which

Re: Redundant SSL virtual host warnings?

On 04/08/2007 08:40 PM, Sander Temme wrote: On Apr 8, 2007, at 11:24 AM, Henrik Nordstrom wrote: Related to this, in current versions of TLS the client MAY advertise which host it is desiring to get connected to which would also require this if implemented in Apache mod_ssl. (server_name

Re: Redundant SSL virtual host warnings?

Me again. Sun, Apr 08, 2007 at 11:43:07PM +0400, Eygene Ryabinkin wrote: In the presence of the subjectAltName with the DNS entries in it, the DNS name of the server SHOULD (if memory servers me right: I am not able to find the reference document now) be checked against the subjectAltName

Re: Redundant SSL virtual host warnings?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ruediger Pluem wrote: This is not a good idea. Even though the client does not complain about a wrong certificate in the case of a wildcard certificate there are still pitfalls on the server side. All virtual host specific SSL configuration