Re: Best practice for restricting access to exact IP addresses
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: users@xxxxxxxxxxxxxxxx
- Subject: Re: Best practice for restricting access to exact IP addresses
- From: Marat Khalili <mkh@xxxxxx>
- Date: Fri, 1 Dec 2017 16:33:48 +0300
- In-reply-to: <8d350542bd598dce1a5abf732c5b3f71.squirrel@sellfam.com>
- Organization: Russian Quantum Center
- Reply-to: users@xxxxxxxxxxxxxxxx
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
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 virtual-host conf file included into the main conf
along with tons of other things.
--
With Best Regards,
Marat Khalili
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
[Index of Archives]
[Open SSH Users]
[Linux ACPI]
[Linux Kernel]
[Linux Laptop]
[Kernel Newbies]
[Security]
[Netfilter]
[Bugtraq]
[Squid]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Samba]
[Video 4 Linux]
[Device Mapper]