>> Without the ServerName, the vhost entry matches everything.
>
> Everything, or the ServerName defined globally?
You're right, good catch. Without the ServerName, the vhost entry matches only
whatever the ServerName is defined as globally
(which is the ServerName outside any containers).
B
On Thu, Jun 2, 2011 at 5:02 PM, Geoff Millikan wrote:
> Poop. It's a simple oversight. Sorry everyone. Tom Evans example works
> just fine. The example from the original post would have
> worked with the addition of a *ServerName*. Without the ServerName, the
> vhost entry matches everythin
Poop. It's a simple oversight. Sorry everyone. Tom Evans example works just
fine. The example from the original post would have
worked with the addition of a *ServerName*. Without the ServerName, the vhost
entry matches everything.
#This doesn't work
RewriteEngine On
RewriteRule .* htt
> You misunderstood what Eric said. The first vhost absolutely can be
> used to redirect requests to another vhost.
> I don't think I can make it any clearer than that - hope that helps.
Wow, thank you! And just for kicks, look back at the original post - you can
see the configuration you propo
On Thu, Jun 2, 2011 at 5:13 PM, Geoff Millikan wrote:
>> Incorrect. The first vhost is ALWAYS used when no vhost with a
>> matching host name is found - it is the catch all vhost, by
>> definition.
>
> Yes, I totally agree. But, the first vhost cannot be used to *redirect
> requests to another v
> Incorrect. The first vhost is ALWAYS used when no vhost with a
> matching host name is found - it is the catch all vhost, by
> definition.
Yes, I totally agree. But, the first vhost cannot be used to *redirect
requests to another vhost.* Per Eric Covener, "You can't
make the catch-all vhost a
Hello all. I have a pair of apache proxy/web-app servers that
simultaneously reported this error this morning. At the time logrotate
was stopping and starting apache.
I've never seen this error before, and teh google isn't giving me
anything useful. I have no proxy statements or redirects in my co
On Thu, Jun 2, 2011 at 2:40 PM, Geoff Millikan wrote:
> In order to have a "catch all" vhost that redirects all hostnames to another
> vhost we must capture everything with a ServerAlias.
> There's no other way.
Incorrect. The first vhost is ALWAYS used when no vhost with a
matching host name is
> Not sure what you mean by crash...
If I put "ServerAlias *" into httpd.conf and try to restart Apache, it will not
start. There's no error log as to why it will not
start.
> The first-listed vhost in a set of namevirtualhosts is the default.
Agreed. However it was said:
> You can't mak
On Wed, Jun 1, 2011 at 9:53 PM, Tommy Peterson
wrote:
> I think I am confused about the directive. How many can you have?
> Can you list 4 or 5, for example, and they are all acted upon? Or does
> Apached just start with the first and stop there. Sorry for such a basic
> question but I ran int
> -Original Message-
> From: Tommy Peterson [mailto:tommy.peter...@xpandcorp.com]
> Sent: Wednesday, June 01, 2011 21:54
> To: users@httpd.apache.org
> Subject: [users@httpd] how many directives can you have?
>
> I think I am confused about the directive. How
> many can you have? Can
I think I am confused about the directive. How many can you have?
Can you list 4 or 5, for example, and they are all acted upon? Or does Apached
just start with the first and stop there. Sorry for such a basic question but I
ran into an issue.
I used such a directive to lock down a particular
On 06/02/2011 01:00 PM, Ravi Chandran wrote:
K, first of all I don't understand the meaning of "Top Post". Can you
specify in layman's term?
It means post your replies either at the bottom of the previous message,
or in-line, below the section you are replying to.
Also, please attribute your r
K, first of all I don't understand the meaning of "Top Post". Can you
specify in layman's term?
second, the focus of this question is only for one Apache installation, as
the other one is working fine, so we don't even need to bother about it..
thirdly, "Same thing" means, seeing the content publ
On 06/02/2011 12:35 PM, Ravi Chandran wrote:
hi,
Please don't top-post.
thanks for replying. Actually we have two systems one on WIFI and one
on LAN, both are running apache web server.
Okay, so we are talking about TWO completely separate apache installations ?
That wasn't entirely clear
hi,
thanks for replying. Actually we have two systems one on WIFI and one on
LAN, both are running apache web server. I am able to access the content
published on the other system using browser. but the same thing is not
happening at the other system. I mean on that system, the content is not
comin
On 06/02/2011 10:43 AM, Ravi Chandran wrote:
hi all,
I have recently downloaded apache http server 2.2, I had published
some content for a project and its working also. Now my requirement is
that this published content should be available across two networks.
So for start, I want to make this
> Ah ha! The issue was that doing "ServerAlias *" crashes Apache with no error
> log. ServerAlias apparently needs more than just a
> single wildcard character. Putting the below entry after the
> last works great! Sweet.
Not sure what you mean by crash, but this is unnecessary. The
first-l
hi all,
I have recently downloaded apache http server 2.2, I had published some
content for a project and its working also. Now my requirement is that this
published content should be available across two networks. So for start, I
want to make this content available on a LAN and WIFI network. How c
19 matches
Mail list logo
