e and progressive as it's always
been.
Timothy D Legg
> On 01/12/17 18:36, Timothy D Legg wrote:
>> and then believes that running a2dissite on all these, perhaps to make a
>> backup of a php-encrusted website (such as mine) that the document root
>> will default to the t
hope this is not true...
> On 01/12/17 15:39, Timothy D Legg wrote:
>
>> To be much more explicit, this is a conf file located in
>> /etc/apache2/sites-available and is the only file symlinked into
>> /etc/apache2/sites-enabled
> It is most likely included into /etc/apache
> On 01/12/17 15:39, Timothy D Legg wrote:
>> There is only one virtualhost active, so it is inherently unique.
>
> Just in case, verify it with: apachectl -D DUMP_VHOSTS
>
>> This is a privacy-sanitized edit of the exact conf file.
>
> This is most likely a virtua
80 in the
first place? I never specified it to do that. There is no
NameVirtualHost *:80 anywhere in this configuration file (to clarify on
the other commenter, this is in sites-enabled/ and is the only file/link
in that folder)
Timothy D. Legg
> While testing, are you sure that youâ
ith that
> directory configuration.
>
> That may very well be an explanation to why it is not happening for
> you. Remember to define a unique servername in each virtualhost,
> different log names for each virtualhost, etc.
>
>
> 2017-12-01 11:28 GMT+01:00 Timothy D Legg :
&g
isor accessing admin tools, such as phpmyadmin.
> you could try /etc/hosts.deny
>
> On Fri, Dec 1, 2017 at 4:03 AM, Timothy D Legg
> wrote:
>
>> Hello,
>>
>> I am wanting to restrict a subdirectory of a website to a single, maybe
>> two, IP addresses.
>>
ip 192.168.40.80
But a test revealed I was able to wget graphs/test.html on a different
machine (192.168.40.81).
I've only read the documentation. Practically every non-Apache website
still uses Order-Allow-Deny methodologies, so it's still not clear how
this is actually done in practice
