On Mon, Sep 12, 2016 at 7:37 PM, Marat Khalili wrote:
> On 12/09/16 18:47, Rainer Canavan wrote:
>> The obvious ones I can come up with would be Alias, ScriptAlias,
>> FastCGIExternalServer,
>> Action and RewriteRule. All those can be defined in the global context
>> (i.e. outside
>> of any vhost)
My thanks to everybody who replied in this thread. I decided just
to take the simple way out, so I added this near the top of my
httpd-vhosts.conf file:
ServerName localhost
ServerAdmin webmas...@tristatelogic.com
DocumentRoot /usr/local/www/apache24/data/localhost/htdocs
Error
On 12/09/16 18:47, Rainer Canavan wrote:
The obvious ones I can come up with would be Alias, ScriptAlias,
FastCGIExternalServer,
Action and RewriteRule. All those can be defined in the global context
(i.e. outside
of any vhost) and are valid for all vhosts. (for RewriteRule, that may require
Rew
On Mon, Sep 12, 2016 at 3:21 PM, Marat Khalili wrote:
> On 12/09/16 15:25, Rainer Canavan wrote:
>>
>>
>> However, in this example, you'd add a virtualhost that may expose
>> globally configured resources without the individual access controls of
>> the "real" vhosts. On top of that, the additiona
On 12/09/16 15:25, Rainer Canavan wrote:
However, in this example, you'd add a virtualhost that may expose
globally configured resources without the individual access controls of
the "real" vhosts. On top of that, the additional vhost may not see any
significant testing in case of configuration
[...]
>> Additionally, if you bind any further vhosts to specific IP addresses, e.g.
>> , then that virtualhost will have precedence for
>> requests to 192.0.2.1:80 over the *:80 virtualhost.
>
> In this case you'll have create separate default deny configuration for each
> IP address, right?
>
>>
On 12/09/16 12:03, Rainer Canavan wrote:
I'm not 100% sure, but that may not deny access to absolutely
everything, in case you have global
directives such as cgi aliases or proxy constructs, possibly with
mod_rewrite and [P] which point
to non-directory resources.
Therefore it may be better t
>>
>> ServerName default
>>
>>
>> AllowOverride none
>> Order Allow,Deny
>> Require all denied
>>
>>
[...]
I'm not 100% sure, but that may not deny access to absolutely everything,
in case you have global
directives such as cgi aliases or proxy constructs, p
There has to be some configuration Apache will use if it cannot match
any virtualhost; or, if no hostname is specified by client. You can make
a configuration that denies access in this case, and put it before
others. That's what I use:
ServerName default
AllowOverride none
On Sun, Sep 11, 2016 at 10:00 PM, Ronald F. Guilmette
wrote:
>>The first one will always be a default. You can make a dedicated one for it.
>
> Thank you. I appreciate your timely reply, however I think that maybe
> you didn't quite get my point and/or my question.
>
> I simply do not want there
On 9/11/2016 19:00, Ronald F. Guilmette wrote:
Eric Covener wrote:
The first one will always be a default. You can make a dedicated one for it.
Thank you. I appreciate your timely reply, however I think that maybe
you didn't quite get my point and/or my question.
I simply do not want there
Eric Covener wrote:
>The first one will always be a default. You can make a dedicated one for it.
Thank you. I appreciate your timely reply, however I think that maybe
you didn't quite get my point and/or my question.
I simply do not want there to exist a default vhost, period.
Isn't there a
On Sun, Sep 11, 2016 at 9:43 PM, Ronald F. Guilmette
wrote:
> How can I get rid of that while still providing service
> for my three vhosts?
The first one will always be a default. You can make a dedicated one for it.
--
Eric Covener
cove...@gmail.com
-
A simple question. Sorry if this is an FAQ.
I'm just bringing up a fresh VM system that I plan to move my small
handful of web sites to.
I'v so far managed to mostly get apache24 installed and configured.
I've moved all of my web sites over to the new system, and it mostly
all seems to be worki
14 matches
Mail list logo
