You haven't shown a need for any proxy configuration at all and you did not
include nearly enough configuration, plus you didn't say what wiki package
you are running.
How about posting more of your config, including the vhost and actual fpm
or mod_php config?
Sent from a gizmo with a very small
I get this error when I try to access my wiki
AH01144: No protocol handler was valid for the URL /wiki/index.php. If you
are using a DSO version of mod_proxy, make sure the proxy submodules are
included in the configuration using LoadModule.
1. For some reason, my linux distribution somehow enabl
On Mon, Jul 20, 2015 at 5:09 PM, Tucker, Doug wrote:
>
>
You may also use DirectoryMatch ([1]) to be more precise/restrictive
about root paths, by using regular expressions.
[1] http://httpd.apache.org/docs/2.4/mod/core.html#directorymatch
--
RESOLVED.
Thank you for the reply. My users have different home directory paths
that do not all originate from the /home so (in my case) from error you
can see in the original post my /users4 is not true for all users, some
are /users and others /users5. I wasn't sure how to handle that and
Hello,
According to http://httpd.apache.org/docs/2.4/mod/core.html#directory :
None of the wildcards match a `/' character, so |"/*/public_html">| will not match |/home/user/public_html|, but
|| will match.
--
With Best Regards,
Marat Khalili
On 20/07/15 17:11, Tucker, Doug wrote:
I'm at
I'm at my wits end. This same configuration works fine on our old
apache 2.2. I have read through the documentation for 2.4 and searched
far and wide but cannot seem to solve this.
I'm running out of the box apache that came with centos 7.
selinux is disabled
Main virtual host setting in the
Hi,
We are facing problem while getting last chunk which looks as below
24;status_upadate=Yes
When apache forwards this chunk to client it removes the part after
semi-colon(;) and hence the client ends up getting a chunk without status.
Is there any configuration wherein apache can avoid manipul
