Re: [users@httpd] php-fpm and proxy , httpd 2.4.12
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 keyboard and hyperactive autocorrect. On Jul 20, 2015 1:25 PM, "MM" wrote: > 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 enabled php-fpm by > default. > My site has very little traffic, and I don't have performance requirements. > > 2. I have the following setting > > > ProxyRequests On > > Order deny,allow > Deny from all > Allow from > > > > Do I need this setting? > > 3.All these modules are loaded > LoadModule proxy_module modules/mod_proxy.so > LoadModule lbmethod_bybusyness_module modules/mod_lbmethod_bybusyness.so > LoadModule lbmethod_byrequests_module modules/mod_lbmethod_byrequests.so > LoadModule lbmethod_bytraffic_module modules/mod_lbmethod_bytraffic.so > LoadModule lbmethod_heartbeat_module modules/mod_lbmethod_heartbeat.so > LoadModule proxy_ajp_module modules/mod_proxy_ajp.so > LoadModule proxy_balancer_module modules/mod_proxy_balancer.so > LoadModule proxy_connect_module modules/mod_proxy_connect.so > LoadModule proxy_express_module modules/mod_proxy_express.so > LoadModule proxy_fcgi_module modules/mod_proxy_fcgi.so > LoadModule proxy_fdpass_module modules/mod_proxy_fdpass.so > LoadModule proxy_ftp_module modules/mod_proxy_ftp.so > LoadModule proxy_http_module modules/mod_proxy_http.so > LoadModule proxy_scgi_module modules/mod_proxy_scgi.so > > and > LoadModule xml2enc_module modules/mod_xml2enc.so > LoadModule proxy_html_module modules/mod_proxy_html.so > > Are there any more modules to load? > >
[users@httpd] php-fpm and proxy , httpd 2.4.12
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 enabled php-fpm by default. My site has very little traffic, and I don't have performance requirements. 2. I have the following setting ProxyRequests On Order deny,allow Deny from all Allow from Do I need this setting? 3.All these modules are loaded LoadModule proxy_module modules/mod_proxy.so LoadModule lbmethod_bybusyness_module modules/mod_lbmethod_bybusyness.so LoadModule lbmethod_byrequests_module modules/mod_lbmethod_byrequests.so LoadModule lbmethod_bytraffic_module modules/mod_lbmethod_bytraffic.so LoadModule lbmethod_heartbeat_module modules/mod_lbmethod_heartbeat.so LoadModule proxy_ajp_module modules/mod_proxy_ajp.so LoadModule proxy_balancer_module modules/mod_proxy_balancer.so LoadModule proxy_connect_module modules/mod_proxy_connect.so LoadModule proxy_express_module modules/mod_proxy_express.so LoadModule proxy_fcgi_module modules/mod_proxy_fcgi.so LoadModule proxy_fdpass_module modules/mod_proxy_fdpass.so LoadModule proxy_ftp_module modules/mod_proxy_ftp.so LoadModule proxy_http_module modules/mod_proxy_http.so LoadModule proxy_scgi_module modules/mod_proxy_scgi.so and LoadModule xml2enc_module modules/mod_xml2enc.so LoadModule proxy_html_module modules/mod_proxy_html.so Are there any more modules to load?
Re: [users@httpd] Cannot get ExecCGI to work with userdir apache 2.4.6
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 - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Cannot get ExecCGI to work with userdir apache 2.4.6
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 tried several different things but adding a wild card for each directory in the path seemed to do the trick. Here is what mine looks like now: Options ExecCGI Indexes FollowSymlinks AllowOverride FileInfo AuthConfig Limit Indexes #AddHandler cgi-script .py .cgi .pl #Require method GET POST OPTIONS Require all granted Just posting this for anyone that might search google to find and answer for. This is different from 2.2 where /*/public_html worked for the entire user directory path. Sincerely, Doug Tucker On 07/20/2015 09:28 AM, Marat Khalili wrote: > 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 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 main httpd.conf is: >> >> >> serveradmine...@lyle.smu.edu >> DocumentRoot "/var/www/html" >> ServerName neodev.seas.smu.edu >> DirectoryIndex index.php index.shtml index.html index.htm >> >> Options Includes FollowSymLinks >> AllowOverride All >> Require all granted >> >> ScriptAlias /cgi-bin/ "/var/www/cgi-bin/" >> >> AllowOverride None >> Options ExecCGI >> Require all granted >> >> ErrorLog logs/neodev-seas-smu-edu-error_log >> CustomLog logs/neodev-seas-smu-edu-access_log combined >> >> >> >> My userdir.conf looks like this: >> >> >> # >> # UserDir is disabled by default since it can confirm the presence >> # of a username on the system (depending on home directory >> # permissions). >> # >> UserDir disabled root >> >> # >> # To enable requests to /~user/ to serve the user's public_html >> # directory, remove the "UserDir disabled" line above, and uncomment >> # the following line instead: >> # >> UserDir public_html >> >> >> # >> # Control access to UserDir directories. The following is an example >> # for a site where these directories are restricted to read-only. >> # >> >> Options Indexes SymLinksIfOwnerMatch IncludesNoExec ExecCGI >> AllowOverride None >> Require all granted >> >> >> Scripts placed in /var/www/cgi-bin work, scripts placed in an user >> directory/cgi-bin do not. The apache logs says this: >> >> Options ExecCGI is off in this directory: >> /users4/enoc/tuckerd/public_html/cgi-bin/doug.py >> >> The directory is 755. >> >> I don't know how more to enable with than with the ExecCGI directive in >> Options. I did try putting the + before each directive but the result >> was the same. Can anyone please shed some light on what I'm missing? >> Again this exact same configuration (with the exception of the Require >> all granted being the old style Allow,deny stuff) works just fine on our >> apache 2.2. >> > - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Cannot get ExecCGI to work with userdir apache 2.4.6
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 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 main httpd.conf is: ServerAdmin e...@lyle.smu.edu DocumentRoot "/var/www/html" ServerName neodev.seas.smu.edu DirectoryIndex index.php index.shtml index.html index.htm Options Includes FollowSymLinks AllowOverride All Require all granted ScriptAlias /cgi-bin/ "/var/www/cgi-bin/" AllowOverride None Options ExecCGI Require all granted ErrorLog logs/neodev-seas-smu-edu-error_log CustomLog logs/neodev-seas-smu-edu-access_log combined My userdir.conf looks like this: # # UserDir is disabled by default since it can confirm the presence # of a username on the system (depending on home directory # permissions). # UserDir disabled root # # To enable requests to /~user/ to serve the user's public_html # directory, remove the "UserDir disabled" line above, and uncomment # the following line instead: # UserDir public_html # # Control access to UserDir directories. The following is an example # for a site where these directories are restricted to read-only. # Options Indexes SymLinksIfOwnerMatch IncludesNoExec ExecCGI AllowOverride None Require all granted Scripts placed in /var/www/cgi-bin work, scripts placed in an user directory/cgi-bin do not. The apache logs says this: Options ExecCGI is off in this directory: /users4/enoc/tuckerd/public_html/cgi-bin/doug.py The directory is 755. I don't know how more to enable with than with the ExecCGI directive in Options. I did try putting the + before each directive but the result was the same. Can anyone please shed some light on what I'm missing? Again this exact same configuration (with the exception of the Require all granted being the old style Allow,deny stuff) works just fine on our apache 2.2.
[users@httpd] Cannot get ExecCGI to work with userdir apache 2.4.6
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 main httpd.conf is: ServerAdmin e...@lyle.smu.edu DocumentRoot "/var/www/html" ServerName neodev.seas.smu.edu DirectoryIndex index.php index.shtml index.html index.htm Options Includes FollowSymLinks AllowOverride All Require all granted ScriptAlias /cgi-bin/ "/var/www/cgi-bin/" AllowOverride None Options ExecCGI Require all granted ErrorLog logs/neodev-seas-smu-edu-error_log CustomLog logs/neodev-seas-smu-edu-access_log combined My userdir.conf looks like this: # # UserDir is disabled by default since it can confirm the presence # of a username on the system (depending on home directory # permissions). # UserDir disabled root # # To enable requests to /~user/ to serve the user's public_html # directory, remove the "UserDir disabled" line above, and uncomment # the following line instead: # UserDir public_html # # Control access to UserDir directories. The following is an example # for a site where these directories are restricted to read-only. # Options Indexes SymLinksIfOwnerMatch IncludesNoExec ExecCGI AllowOverride None Require all granted Scripts placed in /var/www/cgi-bin work, scripts placed in an user directory/cgi-bin do not. The apache logs says this: Options ExecCGI is off in this directory: /users4/enoc/tuckerd/public_html/cgi-bin/doug.py The directory is 755. I don't know how more to enable with than with the ExecCGI directive in Options. I did try putting the + before each directive but the result was the same. Can anyone please shed some light on what I'm missing? Again this exact same configuration (with the exception of the Require all granted being the old style Allow,deny stuff) works just fine on our apache 2.2. -- Sincerely, Doug Tucker - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
[users@httpd] Problem in chunked response
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 manipulating last chunk. Maybe just ignore it. Unfortunately we don't have control over backend server where we could have applied following header Header set X-XSS-Protection: 0 -- Thanks and Regards, Shailender Kumar
