At 08:49 PM 3/25/2006, you wrote:
Ok, my bad, found 2 instances of a default_443. Put only one, but
now neither httpd -DSSL or -k start start apache. Nothing written to error_log.
I wish I could say what I did, but it's working now. :-D
--
At 08:44 PM 3/25/2006, you wrote:
At 07:40 PM 3/25/2006, you wrote:
See if removing the password from the SSLCertificateKeyFile helps.
openssl rsa -in server.pem -out server.key
Thanks for the suggestion.. Getting a little further.
Now if I start httpd -DSSL, I get:
[Sat Mar 25 20:44:26 2006]
At 07:40 PM 3/25/2006, you wrote:
See if removing the password from the SSLCertificateKeyFile helps.
openssl rsa -in server.pem -out server.key
Thanks for the suggestion.. Getting a little further.
Now if I start httpd -DSSL, I get:
[Sat Mar 25 20:44:26 2006] [warn] _default_ VirtualHost overl
See if removing the password from the SSLCertificateKeyFile helps.
openssl rsa -in server.pem -out server.key
- Original Message -
From: "Evan Platt" <[EMAIL PROTECTED]>
To:
Sent: Sunday, March 26, 2006 5:53 AM
Subject: [EMAIL PROTECTED] Secure SSL Site: What am I doing wrong?
Runnin
Running Apache 2.2.0 on a OS/X 10.4 system, compiled from source.
I have mod_ssl enabled.
In my httpd.conf, I have
Include conf/extra/httpd-ssl.conf
in my httpd-ssl.conf, I have
# General setup for the virtual host
SSLEngine on
SSLCertificateFile/Library/Apache2/conf/server.crt
SSL
On Saturday 25 March 2006 23:03, Elver Loho wrote:
> I'm not sure how the RFC specifies this, but I kinda expect Apache to
> default to assuming Connection: close when no keep-alive is specified.
HTTP/1.0 defaults to closing the connection. HTTP/1.1 defaults to
keeping it open. But those are ju
On 3/25/06, Elver Loho <[EMAIL PROTECTED]> wrote:
> Background. We're writing a HTTP client. We don't yet have support for
> keep-alive, so we don't set any keep-alive specific headers
> (connection, keep-alive).
>
> Now, when Apache serves us a page, it drops the connection after
> serving it. Whi
Background. We're writing a HTTP client. We don't yet have support for
keep-alive, so we don't set any keep-alive specific headers
(connection, keep-alive).
Now, when Apache serves us a page, it drops the connection after
serving it. Which is what one would expect if we don't set keep-alive.
Howe
I have CPanel, and i have added an Addon to my Cpanel. Logging for that
domainA.com works.
I then add an alias to httpd.conf to have domainB.com linked to a folder
under my Cpanel's folder (one of domainA.com's subfolder).
Where wil the access.log for domainB.com logged?
Thanks!
---