On 1/31/06, Joshua Slive <[EMAIL PROTECTED]> wrote:
> On 1/31/06, Jason Keltz <[EMAIL PROTECTED]> wrote:
> > On Tue, 31 Jan 2006, Joshua Slive wrote:
>
> > > Use httpd.conf to turn off .htacess processing (AllowOverride) in the
> > > relevant directory inside the section for the non-ssl
> > > host
On 1/31/06, Jason Keltz <[EMAIL PROTECTED]> wrote:
> On Tue, 31 Jan 2006, Joshua Slive wrote:
> > Use httpd.conf to turn off .htacess processing (AllowOverride) in the
> > relevant directory inside the section for the non-ssl
> > host.
>
> Hi Joshua,
>
> Unfortunately, this won't do it since mult
On Tue, 31 Jan 2006, Joshua Slive wrote:
On 1/31/06, Jason Keltz <[EMAIL PROTECTED]> wrote:
An Apache module is enabled on our 1.3.34 https server, and not on our
http server. The http and https servers serve the same document tree.
One .htaccess file in a users web tree (say, ~user/secure/.h
On 1/31/06, Jason Keltz <[EMAIL PROTECTED]> wrote:
> An Apache module is enabled on our 1.3.34 https server, and not on our
> http server. The http and https servers serve the same document tree.
>
> One .htaccess file in a users web tree (say, ~user/secure/.htaccess)
> contains directives that wi
An Apache module is enabled on our 1.3.34 https server, and not on our
http server. The http and https servers serve the same document tree.
One .htaccess file in a users web tree (say, ~user/secure/.htaccess)
contains directives that will only work on the https server. When a
user visits th
