"Ralf S. Engelschall" <[EMAIL PROTECTED]> writes:
> 1. When this is a separate module which does the redirect and
> mod_ssl does nothing more with the variables than just implement them, it
> would be more clean to implement the two directives directly in your own
> module where you do the redirects.
Your assestment is spot on.
I was thinking that one day you would have more than one module loaded at
the same time that might like to have this functionality.
>
> 2. I'm still not convinced whether it's necessary to implement this
> stuff with two new directives. All you need is a way to set server/port and
> fetch these values later. Why not use this:
>
> Listen 80
> Listen 443
>
> SetEnv SSLServerName ssl.foobar.org
> SetEnv SSLServerPort 443
Ah very nice. This works just as well. Thanks.
> Ok, I know you want to do the redirect earlier.
No. I really don't care where the redirect happens. My point on new-httpd
was that given what I had read and seen, it was reasonable for me to assume
that a redirect *could* happen in the post-read phase, not that is *should*
happen there.
-Tom
--
Tom Vaughan <tvaughan at aventail dot com>
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
