But this is not the case - the request was perfectly OK, just took the backend
server too long to handle (note that I am less worried about bogus requests
because this Apache is behind firewall and only serves requests coming from
another component in the system, which is under our control).
I
Xavier Lopez wrote:
I'm still not getting Apache to parse PHP. I've learned a lot though,
here's what I know:
Try asking on the PHP list ...
On SUSE, simply adding php via the packager manager also enables it in a stock
apache installation. SO I suspect you had a working setup and have change
Try the info.php test:
On Wed, Jun 15, 2011 at 10:57:10PM -0700, Xavier Lopez wrote:
> Dear Users,
>
> I'm still not getting Apache to parse PHP. I've learned a lot though,
> here's what I know:
>
> In apache2.conf, there are these lines:
>
> Include /etc/apache2/mods-enabled/*.load
> Inc
Dear Users,
I'm still not getting Apache to parse PHP. I've learned a lot though,
here's what I know:
In apache2.conf, there are these lines:
Include /etc/apache2/mods-enabled/*.load
Include /etc/apache2/mods-enabled/*.conf
When I run ls /mods-enabled, I see php5.conf and php5.load, among othe
On Wed, 15 Jun 2011 23:11:29 +0200
Stefan Fritsch wrote:
Ian> I know that the .htaccess file is getting read, because when I drop
Ian> garbage there I get a server error upon loading that page. So
Ian> somehow the AuthName directive in the .htaccess is getting ignored.
Ian> Why?? AllowOverride s
On 06/15/2011 10:23 PM, Matus UHLAR - fantomas wrote:
On 10.06.11 00:03, Jeroen Geilman wrote:
You need to tell apache what to do with .php files.
This can be implemented - as documented - by adding
SetHandler application/x-httpd-php
in your Documentroot Directory block.
On 06/15/201
>> On 10.06.11 00:03, Jeroen Geilman wrote:
>>> You need to tell apache what to do with .php files.
>>>
>>> This can be implemented - as documented - by adding
>>>
>>>
>>> SetHandler application/x-httpd-php
>>>
>>>
>>> in your Documentroot Directory block.
> On 06/15/2011 10:13 PM, Matus UH
On 06/15/2011 10:13 PM, Matus UHLAR - fantomas wrote:
On 10.06.11 00:03, Jeroen Geilman wrote:
You need to tell apache what to do with .php files.
This can be implemented - as documented - by adding
SetHandler application/x-httpd-php
in your Documentroot Directory block.
Since when th
On 10.06.11 00:03, Jeroen Geilman wrote:
> You need to tell apache what to do with .php files.
>
> This can be implemented - as documented - by adding
>
>
> SetHandler application/x-httpd-php
>
>
> in your Documentroot Directory block.
Since when they recomment something different than AddHa
On Wed, 15 Jun 2011 21:22:28 +0200
Jeroen Geilman wrote:
Ian> > UserDir public_html
Ian> > UserDir disabled root
Ian> >
Ian> >
Ian> > AllowOverride FileInfo AuthConfig Limit Indexes
Ian> > Options MultiViews Indexes SymLinksIfOwnerMatc
On 06/15/2011 08:56 PM, Ian Zimmerman wrote:
I (or rather my distro) enabled userdir as follows:
LoadModule userdir_module /usr/lib/apache2/modules/mod_userdir.so
urgh
UserDir public_html
UserDir disabled root
AllowOverride FileInfo AuthConfig L
On 06/15/2011 09:32 AM, Moshe Ben-Shoham wrote:
Hi,
Thanks for the comment about the ProxyMatch syntax. I will look into
it, although it works.
Regarding the proxy hit, I know for sure that the request should be
proxied because is usually does. It matches the following rewrite rule
(again,
I (or rather my distro) enabled userdir as follows:
LoadModule userdir_module /usr/lib/apache2/modules/mod_userdir.so
UserDir public_html
UserDir disabled root
AllowOverride FileInfo AuthConfig Limit Indexes
Options MultiViews Indexes Sym
On 15 juin 2011, at 15:18, Eric Covener wrote:
>> On the first one (running only on port 80), the Scoreboard properly display
>> 128 slots.
>
> Does this system use the ServerLimit directive?
Oh. You got me. I've added this directive on the first server a while ago, and
totally forgot about i
On Wed, Jun 15, 2011 at 8:57 AM, Patrick Proniewski
wrote:
> On 15 juin 2011, at 13:25, Bostjan Skufca wrote:
>
>> This is the extract from source file server/mpm/prefork/prefork.c:
>> ../..
>> #ifndef DEFAULT_SERVER_LIMIT
>> #define DEFAULT_SERVER_LIMIT 256
>> #endif
>
> I would say "ok", if all
Please ignore that mail
I have pressed SEND without checking.
2011/6/15 Petr Hracek :
> Dear users,
>
> I have a some problems with proxy authorization and I could not make
> an authorization of the proxy pages.
>
> Configuration in my :
>
>
> SSLEngine on
> SSLProxyEngine on
> ProxyRequests off
Dear users,
I have a some problems with proxy authorization and I could not make
an authorization of the proxy pages.
Configuration in my :
SSLEngine on
SSLProxyEngine on
ProxyRequests off
RewriteEngine on
RewriteCond %{REQUEST_METHOD} ^TRACE
RewriteMap pages txt:/opt/httpd2/conf/pages.txt
Rew
On 15 juin 2011, at 13:25, Bostjan Skufca wrote:
> This is the extract from source file server/mpm/prefork/prefork.c:
> ../..
> #ifndef DEFAULT_SERVER_LIMIT
> #define DEFAULT_SERVER_LIMIT 256
> #endif
I would say "ok", if all my servers would behave the same. But no.
On two almost identical serve
CentOS implies SELinux, that won't allow random execution.
- Original Message -
> Hi,
> when I try to execute a php order using shell_exec or backtick
> operator, the command never returns anything. Also, appears a new
> line
> in error_log file each time php file is called from url, with
This is the extract from source file server/mpm/prefork/prefork.c:
/* Limit on the total --- clients will be locked out if more servers than
* this are needed. It is intended solely to keep the server from c
Hi,
when I try to execute a php order using shell_exec or backtick
operator, the command never returns anything. Also, appears a new line
in error_log file each time php file is called from url, with the next
information:
sh: hostname: command not found.
I've tried to put the complete path
Hello,
I'm using Munin to monitor few Apache servers.
The apache_processes plugin parse the output of
http://127.0.0.1:80/server-status?auto , which looks like this:
Total Accesses: 20492
Hi,
Thanks for the comment about the ProxyMatch syntax. I will look into it,
although it works.
Regarding the proxy hit, I know for sure that the request should be proxied
because is usually does. It matches the following rewrite rule (again, URL was
changed):
RewriteRule ^/x/y(.*) http:/
On 06/15/2011 08:52 AM, Moshe Ben-Shoham wrote:
Hi,
We're using Apache 2.2.15, with mod_proxy_http for proxying requests
to backend processes.
Here's the relevant configuration we use:
http://localhost:9001>
That is not valid syntax for ProxyMatch, which requires a regular
expression.
P
24 matches
Mail list logo
