Le 1 octobre 2013 à 22:25, Eric Covener a écrit :
> Don't use domains or IP addresses inside or
> NameVirtualHost. It's causing two sets of name-based vhosts. Use
> *:80.
Hi,
When I did that, and restarted the server and then went to my URL, I got a
warning about the certificate not being ap
Leo:
Its start fine when I run it from the command line.
On Tue, Oct 1, 2013 at 12:28 PM, Leo Donahue - RDSA IT <
leodona...@mail.maricopa.gov> wrote:
> From: Ezra Taylor [mailto:ezra.tay...@gmail.com]
> Sent: Tuesday, October 01, 2013 7:34 AM
> To: users@httpd.apache.org
> Subject: Re:
Hello everyone and a special hello to this list's regular.
I'm trying to figure out why I can't access some directories over my
Apache 2.4.6 web server.
There are two machines, the web server which is also the local machine,
thus matching both 127.0.0.1 and 192.168.1.101 in my network and my
Andr
Top-posting, as it seems to be the trend.
This is a portion of how our environment is set up. We have multiple
virtual hosts, and two with SSL. We run configurations like this on CentOS
6.4 server with the latest updates.
We use a SAN cert to manage multiple domain names.
Please note that thes
Don't use domains or IP addresses inside or
NameVirtualHost. It's causing two sets of name-based vhosts. Use
*:80.
On Tue, Oct 1, 2013 at 4:06 PM, John McIntyre wrote:
> So I'm still unable to serve that domain2.com :(
>
>
>
>
> Le 1 octobre 2013 à 18:04, Nick Tkach a écrit :
>
> Okay, if yo
So I'm still unable to serve that domain2.com :(
Le 1 octobre 2013 à 18:04, Nick Tkach a écrit :
> Okay, if you're not doing ssl on domain2 then, no, that's not related. I
> thought maybe from the post title that you were asking about virtual hosts
> for ssl and that gets complicated depen
Hi,
I've been searching though the archive and I haven't been able to find a
posting that talks about exactly the problem we're having, so I hope folks will
be patient if I'm duplicating some questions here.
I'm running a test system which hosts several applications, one of which is
required to
Okay, if you're not doing ssl on domain2 then, no, that's not related. I
thought maybe from the post title that you were asking about virtual hosts
for ssl and that gets complicated depending on exactly what you're trying
to do.
On Tue, Oct 1, 2013 at 11:57 AM, John McIntyre wrote:
> Hi,
> Tha
Hi,
Thanks for that. Unfortunately, even after the changes, entering domain2.com
on a browser still goes directly to domain1.com.
No, I don't have any intention to do SSL on domain2.com. Is this causing a
problem?
D.
Le 1 octobre 2013 à 17:29, Nick Tkach a écrit :
> Well, question is, are
thanks, committed to trunk and proposed for 2.4.x
On Tue, Oct 1, 2013 at 11:03 AM, David Hawes wrote:
> When performing subgroup searches, an LDAP search with scope base is
> issued on the DN of a group with a hard-coded filter of "cn=*". If the
> group does not have a cn, the search will fail.
>
Well, question is, are you trying to have domain2.com *also* do that same
http->https ( http://domain2.com to https://domain2.com )? If so, do you
have separate certificates for each (domain1 and domain2)?
On Tue, Oct 1, 2013 at 10:36 AM, Pete Houston wrote:
> On Tue, Oct 01, 2013 at 04:25:05P
From: Ezra Taylor [mailto:ezra.tay...@gmail.com]
Sent: Tuesday, October 01, 2013 7:34 AM
To: users@httpd.apache.org
Subject: Re: [users@httpd] AuthType Digest or AuthType Basic not workin in
Apache 2.4.6
Hello Leo:
Below is what I have. I used htdigest to create a file name "somefile"
an
UNSUBSCRIBE
From: John McIntyre [mailto:joh98@gmail.com]
Sent: Tuesday, October 1, 2013 10:25 AM
To: users@httpd.apache.org
Subject: [users@httpd] Virtual Hosts Possible for SSL ?
Hi,
I have an apache 2.2.15 instance running on a CentOS 6.4 server.
This server is (or will be, if
Hi,
I have an apache 2.2.15 instance running on a CentOS 6.4 server.
This server is (or will be, if I ever get it working...) two domains. One
of them has an SSL certificate, and one doesn't. I've been struggling with
this for two days solid, and if my research is correct, then the SSL
handshake
On Tue, Oct 01, 2013 at 04:25:05PM +0100, John McIntyre wrote:
> Am I doomed to failiure, or is what I'm trying to do, actually possible?
No, you are almost there. The problem is that for some reason you have
an asterisk in your VirtualHost declaration for domain2. Change that the
the actual IP ad
When performing subgroup searches, an LDAP search with scope base is
issued on the DN of a group with a hard-coded filter of "cn=*". If the
group does not have a cn, the search will fail.
Since we simply want to get the group members, the default filter of
"objectClass=*" should be used.
A patch
Hello Leo:
Below is what I have. I used htdigest to create a file name
"somefile" and I specified the realm name realm. Note, I'm using a RHEL
clone from Amazon named "Amazon Linux AMI release 2013.03". Note, this
work in version Apache 2.2 but not in 2.4.6 for some reason. Thanks for
you
On Tue, Oct 1, 2013 at 10:02 AM, Redalert Commander <
redalert.comman...@gmail.com> wrote:
> Our configuration has the typical include of
> "/etc/httpd/conf.d/*.conf", it is here that the vhosts are defined in
> separate files. Should the default also be placed in here or does it
> have to be defi
Hi,
I was reading the documentation and testing out some things.
We have multiple name based virtual hosts, but would like to display a
page when not match is found.
According to the documentation at [1] and [2], the first matching
servername or alias is used, with no precedence for wildcards.
Wh
./configure should default to the same type as the system you are running
it on.
You can override it with the correct environment variables set when you
call configure (I think it is something like CFLAGS="-m32" CPPFLAGS="-m32"
LDFLAGS="-L/usr/lib32" to build x86 on x64)
- Y
On Tue, Oct 1, 2013
Dear Expert,
I am wondering apache 2.4.6 for UNIX available at
"http://httpd.apache.org/docs/2.4/ " .
Is it 64 bit or 32 bit or it depends on the machine we compile.
Thanks and Regards
Rajeev
On Mon, Sep 30, 2013 at 06:03:37PM -0700, Andrew Daviel wrote:
> huh! wtf? - if I enable /server-status, the correct address for the
> client asking for /server-status, is not just logged, but resolved,
> even though HostnameLookups is off. But other requests still get the
> 98.32 address.
This r
22 matches
Mail list logo
