check this link for very good articles www.debianhelp.co.uk/webserver.htm thanksBoyle Owen <[EMAIL PROTECTED]> wrote: > -Original Message-> From: Jerry Baker [mailto:[EMAIL PROTECTED]> > I guess another way of putting it is, I am looking to see if it is > possible to just tell Apa
Boyle Owen wrote:
suffice to say that if your understanding of the functioning of HTTP were
accurate, it would be trivial to do what you want.
If it was trivial to accomplish, you would have explained how. My
apologies. I thought this was a list where Apache users request
assistance. I don't
> -Original Message-
> From: Jerry Baker [mailto:[EMAIL PROTECTED]
>
> It's not wrongthink.
I don't want to get into a big debate - suffice to say that if your
understanding of the functioning of HTTP were accurate, it would be trivial to
do what you want.
Rgds,
Owen Boyle
Disclaimer:
Boyle Owen wrote:
First, the lecture:
"...just to include SSL." is your wrongthink.
It's not wrongthink. I don't know what users are going to want to
protect, and what they aren't. I make everything potentially protected
by SSL and I'll let them use .htaccess and SSLRequireSSL to protect the
Nick Burch wrote:
Include /etc/httpd/partial-sites/foo.conf
SSLEngine on
SSLCertificateFilessl/foo.crt
SSLCertificateKeyFile ssl/foo.pem
SSLCACertificateFile ssl/CA_Test.crt
Include /etc/httpd/partial-sites/foo.conf
This is *exactly* what I have now, but it jus
> -Original Message-
> From: Jerry Baker [mailto:[EMAIL PROTECTED]
>
> I guess another way of putting it is, I am looking to see if it is
> possible to just tell Apache that anything on port 443 is to
> be treated
> as SSL and anything on port 80 is to be treated as normal
> HTTP? It s
On Mon, 19 Dec 2005, Jerry Baker wrote:
Currently I have to set up one container for "regular" port 80 access
and another container for SSL access. Since each virtual host has a
large and massively different configuration than the others, it is a
pain to make sure that the port 80 vhost and the
Hi,
The httpd.conf file has four LogFormat lines like below. The actual log shows
only one line per access request. The first line has everything combined so why
four entries?
-# remoteHost, identityCheck, userName, time, first line of the
request, status, bytes sent
Jerry Baker wrote:
Is there
a way to configure a vhost so that the "regular" access and SSL access
use the same configuration (other than using config file includes)?
I guess another way of putting it is, I am looking to see if it is
possible to just tell Apache that anything on port 443 is t
I have several name-based virtual hosts up and running with no issues,
and the same for SSL. However, I get the feeling that the way I have it
currently is not the optimum way. Currently I have to set up one
container for "regular" port 80 access and another container for SSL
access. Since each
10 matches
Mail list logo
