Geoffrey Young wrote:
>
> Geoffrey Young wrote:
>
That sounds like a job for Apache to do. Apache knows what modules are
compiled in, so it can check that list before trying to LoadModule.
You may want to suggest that to the Apache developers. Most likely any
Apache module suffe
Geoffrey Young wrote:
>>>That sounds like a job for Apache to do. Apache knows what modules are
>>>compiled in, so it can check that list before trying to LoadModule.
>>>You may want to suggest that to the Apache developers. Most likely any
>>>Apache module suffers from this problem.
ok, as it t
Rici Lake wrote:
Obviously, this requires some careful thought to get right, but a good
rule of thumb is: put your Location sections in order in the file,
from least-specific to most-specific. Then things will probably work
out the way you would expect them too.
I gave it some careful thought,
Hi, Ben (and modperl folken)
I've pieced together your config file from the bit's you've sent me and
posted; I deleted the ip numbers, but here is what I think it basically
looks like:
# Doesn't work
SetHandler server-status
Order deny,allow
Deny from all
Allow from xx.xx.xx.xx
A
On Mon, Sep 06, 2004 at 03:31:51PM -0700, Ben Hopkins wrote:
> Here's the error log entries:
> [Mon Sep 6 15:21:44 2004] [error] [client 4.42.113.186] File does not
> exist: /usr/local/apache/htdocs/server-status
> [Mon Sep 6 15:22:03 2004] [error] [client 4.42.113.186] File does not
> exist: /
William McKee wrote:
On Sat, Sep 04, 2004 at 12:56:26PM -0700, Ben Hopkins wrote:
I got FORBIDDEN errors until I put my IP addr (I'm working on a remote
server). Then I got 404s.
The directives look similar to mine. Is there no message in the Apache
error logs that gives you a hint of wha
On Sat, Sep 04, 2004 at 12:56:26PM -0700, Ben Hopkins wrote:
> I got FORBIDDEN errors until I put my IP addr (I'm working on a remote
> server). Then I got 404s.
The directives look similar to mine. Is there no message in the Apache
error logs that gives you a hint of what's wrong with your syst
>> That sounds like a job for Apache to do. Apache knows what modules are
>> compiled in, so it can check that list before trying to LoadModule.
>> You may want to suggest that to the Apache developers. Most likely any
>> Apache module suffers from this problem.
>
>
> I thought that's what I was
Stas Bekman wrote:
Ben Hopkins wrote:
William McKee wrote:
On Fri, Sep 03, 2004 at 10:47:37PM -0700, Ben Hopkins wrote:
The very odd thing is that there are no errors in the build, or
in apache's logs or when it tries to run a module.
What kind of error are you expecting? Perhaps mod_perl does
Ben Hopkins wrote:
William McKee wrote:
On Fri, Sep 03, 2004 at 10:47:37PM -0700, Ben Hopkins wrote:
The very odd thing is that there are no errors in the build, or
in apache's logs or when it tries to run a module.
What kind of error are you expecting? Perhaps mod_perl does not mind tw
William McKee wrote:
On Fri, Sep 03, 2004 at 10:47:37PM -0700, Ben Hopkins wrote:
The very odd thing is that there are no errors in the build, or in
apache's logs or when it tries to run a module.
What kind of error are you expecting? Perhaps mod_perl does not mind two
versions being l
On Fri, Sep 03, 2004 at 10:47:37PM -0700, Ben Hopkins wrote:
> THAT DID IT! I commented perl's LoadModule, restarted, and VIOLA,
> every thing's back to normal.
Hey Ben,
I'm glad that Rici was able to help you.
> The very odd thing is that there are no errors in the build, or in
> apach
Rici Lake wrote:
On 2-Sep-04, at 10:51 PM, Ben Hopkins wrote:
Nope. There are two copies of libperl.so: one in the apache source
tree, and one in libexec.
That's normal. libperl.so is created in the source tree and then
copied into the right
place when you do make install.
However, you seem to
William McKee wrote:
On Thu, Sep 02, 2004 at 08:51:15PM -0700, Ben Hopkins wrote:
Nope. There are two copies of libperl.so: one in the apache source
tree, and one in libexec.
BUT that link said to use ldd to see what libperl.so is referenced in
the httpd executable. I did that and found N
On Thu, Sep 02, 2004 at 08:51:15PM -0700, Ben Hopkins wrote:
> Nope. There are two copies of libperl.so: one in the apache source
> tree, and one in libexec.
>
> BUT that link said to use ldd to see what libperl.so is referenced in
> the httpd executable. I did that and found NO reference to
William McKee wrote:
Sorry to hear about the hair loss and damage to your walls. I'm starting
to think that you may be running into a problem that I've hit
before--having an extra libperl.so laying around. Check out this thread
between Stas and myself for more info[1]. I've given you the link to th
Hi Ben,
Sorry to hear about the hair loss and damage to your walls. I'm starting
to think that you may be running into a problem that I've hit
before--having an extra libperl.so laying around. Check out this thread
between Stas and myself for more info[1]. I've given you the link to the
last messa
William McKee wrote:
On Tue, Aug 31, 2004 at 08:41:10PM -0700, Ben Hopkins wrote:
2: I added /perl-status and got a 404 error, just like I get for
/server-status, /server-info, and /howdy locations. _It's exactly as if
mod_perl were not installed!_
Wait a minute! It is exactly as if the "
Rici Lake wrote:
On 31-Aug-04, at 10:41 PM, Ben Hopkins wrote:
...
I could be way out to lunch here, but what section of your site are
you proxying?
mod_proxy causes any SetHandler in a proxied location to be ignored.
In fact, it
causes any handler in a proxied location to be ignored, since it j
On Tue, Aug 31, 2004 at 08:41:10PM -0700, Ben Hopkins wrote:
> 2: I added /perl-status and got a 404 error, just like I get for
> /server-status, /server-info, and /howdy locations. _It's exactly as if
> mod_perl were not installed!_
>
> Wait a minute! It is exactly as if the "SetHandler" di
William McKee wrote:
On Mon, Aug 30, 2004 at 09:51:14PM -0700, Ben Hopkins wrote:
I'm running RH 8, apache 1.3.23, mod_perl 1.29.
Have you tried compiling with a newer version of Apache? It's up to
release 1.3.31 now. I'm pretty sure that mod_perl 1.29 was released
several months after the
On Mon, Aug 30, 2004 at 09:51:14PM -0700, Ben Hopkins wrote:
> I'm running RH 8, apache 1.3.23, mod_perl 1.29.
Hi Ben,
Have you tried compiling with a newer version of Apache? It's up to
release 1.3.31 now. I'm pretty sure that mod_perl 1.29 was released
several months after the release of Apach
I'm running RH 8, apache 1.3.23, mod_perl 1.29. They wanted me to
install a CMS (Plone) that uses Zope, which requires that I put
mod_proxy into the apache setup. So I redid the apache ./configure
(forgetting about mod_perl for the moment).
Then I remembered about mod_perl, learned about APAC
23 matches
Mail list logo
