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,
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 hi
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
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
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
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
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
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 i
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
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
sever
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
11 matches
Mail list logo
