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 13:45:12 +0300
- In-reply-to: <304d8817-e56d-a332-ab34-6aa7d1a6a1af@rqc.ru>
- 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 13:42, Marat Khalili wrote:
Most likely it is overridden by other Directory or Location or some
other kind of block somewhere in your configuration. Try to replace
<Directory /var/www/html/graphs> with <Location /graphs> to be closer
to the end of pipeline as described here:
https://httpd.apache.org/docs/current/sections.html#merging
P.S. Correction: second most likely. Most likely cause is incorrect
virtualhost indeed.
--
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]