Thank you everyone for the replies, I will go ahead and configure it and
will let the forum know if I encounter any issues
On 1 Dec 2017 10:52 am, "William A Rowe Jr" wrote:
> According to my notes, that is 2.2.15.
>
> As noted previously, turn to RH for support. The EOL was back in July and
> w
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 top level of all these sites and perhaps reveal SQL
passwords in the process.
I hope this
That is almost identical to what I discovered independently. I read every
active .conf file in entirety to realize this.
I was on the assumption that from a web client perspective, a2dissite on
all sites had the same effect as stopping apache, essentially forcing it
idle. It appears that a2dissi
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/apache2/apache2.conf or
/etc/apache2/httpd.conf . Which most likely
> 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
That is a valid, and very interesting point...
I did the request under port 80, and it loaded. I completely forgot that
I never enabled port 80.
This configuration is for port 443.
Again, I never configured it to listen to port 80.
So... where on earth did it get configured to listen on port
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
Directory points to a real filesystem path and does not need trailing slashes.
Use:
AllowOverride none
Require ip 172.12.33.177
To make sure you are not landing in other virtualhost, check apachectl
-S output, there can be none with the same servername as this one
2017-12-01 13:5
On Fri, Dec 1, 2017 at 7:39 AM, Timothy D Legg wrote:
> There is only one virtualhost active, so it is inherently unique.
>
> I tried the following:
>
>
>
>
>
>
Only the first has any effect.
-
To unsubscribe
While testing, are you sure that you’re accessing it over HTTPS and not
HTTP? If this is over normal HTTP, then none of your below configuration
will apply.
--
Osama Elnaggar
On December 1, 2017 at 11:39:11 PM, Timothy D Legg (apa...@timothylegg.com)
wrote:
There is only one virtualhost active
There is only one virtualhost active, so it is inherently unique.
I tried the following:
I have not tried:
but I suspect that this isn't where the problem lies.
This is a privacy-sanitized edit of the exact conf file. By the way, I
did reload the server on each modifi
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
with to be closer
to the end of pipeline as described here:
https://httpd.apache.org/docs/current/sections.html#merg
I added these lines inside the block:
Require 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 st
Make sure you are really landing in the same virtualhost with 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:
In my scenario, that might work, and I appreciate the elegance of
high-order switches to access. However, my exact question would lead to a
more useful solution for myself and others.
Lets consider, for example, I created a dashboard in PHP for modifying my
SQL database. It would be best to have
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.
>
> I will refer to this documentation:
>httpd.apache.org/docs/current/howto/access.html
> under the s
Hello,
I am wanting to restrict a subdirectory of a website to a single, maybe
two, IP addresses.
I will refer to this documentation:
httpd.apache.org/docs/current/howto/access.html
under the section "Access control by host".
This document suggests that 'Allow', 'Order', and 'Deny' are deprec
17 matches
Mail list logo
