On Tue, Jan 09, 2007 at 02:22:13PM -0500, Nelson Castillo wrote..
> >I created ssl certicates by openssl sucseccfull for each domain
> >there is no problem with certificates and keys) like
> >https://www.domain1.com https://www.domaian2.com something like
> >this...
> >>
> >1. Please don't
> My aaim is to run multi domains on apache server with ssl support. ( I
created ssl certicates by openssl sucseccfull for each domain there is no problem
with certificates and keys) like https://www.domain1.com https://www.domaian2.com
something like this...
>
1. Please don't post entire
On Tue, Jan 09, 2007 at 07:25:05AM -0800, Nevruz Mesut Sahin wrote:
> Dear Friends first I am going to tell you my aim then what I did and resoult.
> on my system is kernal 2.6 and apache 2.2 is running.
>
> My aaim is to run multi domains on apache server with ssl support. ( I
> created ssl
sockets available, shutting down
Unable to open logs
then I put orginal httpd.conf and ssl.conf files and I tried to start
server but it give same error.
You will have to use different ports for each virtual domain.
Regards.
--
http://arhuaco.org
http://emQbit.com
--
To UNSUBSCRIBE, email to
certificates and keys) like https://www.domain1.com
https://www.domaian2.com something like this...
then I get backup of httpd.conf and ssl.conf files. Then I configured it shown
like above.
then I get error like this:
httpd start: [Tue Jan 09 15:51:09 2007] [warn] module ssl_module is already
On Mon, Sep 19, 2005 at 08:58:52AM +0200, David Huemer wrote:
> By the way: I would absolutetly recommend to compile the apache2 by
> hand so you can define your own profile in the config.layout file to
> customize where config files and so on are located.
That seems like rather a lot of work, whe
On Mon, Sep 19, 2005 at 09:13:31AM -0700, Jared Hall wrote:
> In a way, I guess that this means httpd.conf is obsolete, since
> apache2.conf only includes httpd.conf... but that's more a matter of
> perspective. httpd.conf needs to be there for apt to properly install
> php5
G_FILE="conf/apache2.conf"
What I meant to say originally was just a minor aside about changing
this (httpd.conf seems to be accepted everywhere else) to apache2.conf,
and then using an include for httpd.conf (hint: Include
/etc/apache2/httpd.conf) is sort of unneccessary. But no bi
On mandag 19 september 2005, 18:13, Jared Hall wrote:
> No, httpd.conf is not obsolete. Anything you stick into it will
> still operate as it did before (default configuration).
Yep, you're right, and indeed it is Included. I also found that I
enabled RewriteEngine in there... :-) It
On 9/19/05, David Huemer <[EMAIL PROTECTED]> wrote:
> I prefer httpd.conf too, but deleting the apache2.conf is no good idea.
> The only good thing about the apache2.conf is, that it includes the
> httpd.conf so all user defined configuration can be done in the
> httpd.conf an
I prefer httpd.conf too, but deleting the apache2.conf is no good idea.
The only good thing about the apache2.conf is, that it includes the
httpd.conf so all user defined configuration can be done in the
httpd.conf and they can be seen very easily. But that is also possible
if you include a
rtain
times)? code consolidation = efficiency.
I agree. Right now apache is compiled to use apache2.conf as the config
file, and then apache2.conf has a line to include httpd.conf. Why
couldn't httpd.conf have just had a line at the top to include apache2.conf?
--
To UNSUBSCRIBE, email
Debian Users
>>The README file that came with Debian doesn't cover the difference
>>between the httpd.conf file and the apache2.conf file. Is the
>>httpd.conf file basically obsolete?
> >
> >I haven't had time to look into it at depth, but I think the
Kjetil Kjernsmo wrote:
On mandag 19 september 2005, 06:53, Steve Dondley wrote:
The README file that came with Debian doesn't cover the difference
between the httpd.conf file and the apache2.conf file. Is the
httpd.conf file basically obsolete?
I haven't had time to lo
David Huemer wrote:
I tried the provided .deb package and also compiled my own apache2
server and discovered the following: If you use the Debian package all
configuration is done in the apache2.conf and the httpd.conf is only for
compatibility reasons. If you compile your own server, all
oo, but Debian is easier to work with
in my environment.
On Apache
yeah, Apache really spread the httpd.conf file all over the place.
Eventually I'll get used to it. just getting into the hang of it now.
I hated it at first, but then I reflected on the past and how it was
getting a bit annoyi
On Mon, Sep 19, 2005 at 08:58:52AM +0200, David Huemer wrote:
> I tried the provided .deb package and also compiled my own apache2
> server and discovered the following: If you use the Debian package all
> configuration is done in the apache2.conf and the httpd.conf is only for
> c
Well, as I pointed out, the README file ins't very clear in its
description of httpd.conf. It just says "empty file".
On 9/19/05, Ross Boylan <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 19, 2005 at 08:26:37AM +0200, Kjetil Kjernsmo wrote:
> > On mandag 19 september 20
I tried the provided .deb package and also compiled my own apache2
server and discovered the following: If you use the Debian package all
configuration is done in the apache2.conf and the httpd.conf is only for
compatibility reasons. If you compile your own server, all configuration
files are in
On Mon, Sep 19, 2005 at 08:26:37AM +0200, Kjetil Kjernsmo wrote:
> On mandag 19 september 2005, 06:53, Steve Dondley wrote:
> > The README file that came with Debian doesn't cover the difference
> > between the httpd.conf file and the apache2.conf file. Is the
> >
On mandag 19 september 2005, 06:53, Steve Dondley wrote:
> The README file that came with Debian doesn't cover the difference
> between the httpd.conf file and the apache2.conf file. Is the
> httpd.conf file basically obsolete?
I haven't had time to look into it at dep
The README file that came with Debian doesn't cover the difference
between the httpd.conf file and the apache2.conf file. Is the
httpd.conf file basically obsolete? Should I just put all directives
and containers in apache2.conf file? Does it matter?
--
Dondley Communications
So I take it this is a local lan, not to be seen on the internet, I don't
think this would really work for me but thanks for the input.
> I am hosting 3 sites using vhosts. Here are the only parts of the
> conf file that are related.
>
>
> DocumentRoot /var/www/
> ServerName buddy.mtntop.home
>
This appears at the very end of my httpd.conf in the /etc/apache directory
hopefullywhen you add these lines and uncomment and customize this conf.
you're question mite be answeredSubin.
# SSL--
# This is an example configuration
sorry correction Monique to my previous email
the configuration exists in the /etc/apache-ssl/httpd.conf
file
Subin.
- Original Message -
From: "Monique Y. Mudama" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 20, 2004 12:30 PM
Subject: Re: htt
On 2004-04-20, Linux Nick penned:
> This is a multi-part message in MIME format.
>
> --=_NextPart_000_0048_01C426B2.FD4F8DE0 Content-Type: text/plain;
> charset="US-ASCII" Content-Transfer-Encoding: 7bit
>
> Does anyone have a working httpd.conf file that they cou
Linux Nick([EMAIL PROTECTED]) is reported to have said:
> Does anyone have a working httpd.conf file that they could send me, directly
> or to the list? One that is hosting 2 sites in vhosts. Im really looking for
> one that is hosting on secure and one that is unsecure, but ill take j
Does anyone have a working httpd.conf file that they could
send me, directly or to the list? One that is hosting 2 sites in vhosts. Im
really looking for one that is hosting on secure and one that is unsecure, but
ill take just one with 2 working vhsots. Im tired of looking at
“sample
I recently installed apache-perl on my home machine. When I try to run
the executable (/usr/sbin/apache-perl), I get the error message:
apache-perl: could not open document config file
/etc/apache-perl/httpd.conf
Sure enough, there is no httpd.conf in /etc/apache-perl. There is,
however
29 matches
Mail list logo
