> Anyway, order matters.
Order of sections doesn't matter in practice. is overridden by anything conceptually underneath it no matter the
config ordering.
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For
Didn't include any other configs. The *only* things I changed on the
repositories was to add the Alias and Directory stanza.
On Mon, Oct 29, 2018 at 7:17 AM Gillis J. de Nijs
wrote:
> No, just that you can "Include" other configurations, and if you don't do
> that, it won't work (duh...). I'm
No, just that you can "Include" other configurations, and if you don't do
that, it won't work (duh...). I'm assuming you did that correct, or
specified them right there in the httpd.conf. The other option is that you
did include the configs, but the " block is after your
included configurations.
Hey Gillis, what do you mean by "not included"? Maybe I missed something.
We have two of these repositories, "updates" and "optional". Their
configs are at the end of the httpd.conf file and they just have the
"Alias" and "Directory" settings. They are also on a separate filesystem
from the
The only other thing I can think of right now is that either the config is somehow not included (but in
that case the Alias probably wouldn't work either), or it is before the
block, which then overrides the former. All of this is
assuming that you only have two blocks in your config. Anyway,
Hey Jonathon, SELinux is on permissive. Checked that early on. :)
The biggest clue for me seems to be that if we open up the "/>" to Allow by default things work. Otherwise they don't.
Leam
On 10/28/18 9:26 AM, Jonathon Koyle wrote:
It may be getting denied by SELinux, I suspect the label on
I missed a slash in that regular expression (/.*)? rather than (.*)?
On Sun, Oct 28, 2018, 07:26 Jonathon Koyle wrote:
> It may be getting denied by SELinux, I suspect the label on your aliased
> directory die not allow httpd access. You will likely need to look into
> semanage, something like
It may be getting denied by SELinux, I suspect the label on your aliased
directory die not allow httpd access. You will likely need to look into
semanage, something like this may do what you need, but I'm not an expert
at SELinux myself... redhat provides some explanation here:
On 10/27/18 7:49 AM, Eric Covener wrote:
On Sat, Oct 27, 2018 at 7:29 AM Leam Hall wrote:
The only fix seems to be making the "" more open than we
want. It seems like Apache can't handle a more open sub-directory than
whatever is allowed for the root directory.
Apache can handle that just
On Sat, Oct 27, 2018 at 7:29 AM Leam Hall wrote:
>
> The only fix seems to be making the "" more open than we
> want. It seems like Apache can't handle a more open sub-directory than
> whatever is allowed for the root directory.
Apache can handle that just fine. Show the smallest verbatim
The only fix seems to be making the "" more open than we
want. It seems like Apache can't handle a more open sub-directory than
whatever is allowed for the root directory.
On 10/26/18 5:34 AM, Leam Hall wrote:
Hey Gillis, I set the log level to debug and all it said was that the
server
Hey Gillis, I set the log level to debug and all it said was that the
server configuration prevented the operation. One line.
What we have done so far is set the "Directory /" to "Order deny,allow"
and then "Deny from all", and then set "Order allow,deny" and "Allow
from all" on the Alias. So
For any troubleshooting, your starting point should be the error log. It
usually explains pretty well why something is forbidden.
On Thu, Oct 25, 2018 at 9:52 PM Leam Hall wrote:
> Following the Alias docs (
> https://httpd.apache.org/docs/2.2/mod/mod_alias.html#alias) and it's not
> working.
Following the Alias docs (
https://httpd.apache.org/docs/2.2/mod/mod_alias.html#alias) and it's not
working. Debug is turned on and i know some security stuff has been done to
the config. Since mod_alias is still there, what else could prevent an
Alias from getting a "Forbidden".
If I take an
14 matches
Mail list logo
