Re: custom directives, again...

[Noam Solomon]

To solve the second problem (Apache::Icon not loading its directives
properly), I ended up commenting out all the "AddModule" statements as well
as the "ClearModuleList" statement in the httpd.conf fiile.  I don't really
know why this fixed the problem, but I suppose it's related to having
statically compiled all the basic modules directly into the httpd binary.
The answer came to me when I belatedly remembered having encountered a
similar problem a couple months ago on my development server, where I had
httpd dynamically loading its binaries, and the problem then turned out to
be that I had some modules loading in the wrong order.

Hope this helps someone somewhere down the line!

- Original Message -
From: "Per Einar Ellefsen" <[EMAIL PROTECTED]>
To: "Noam Solomon" <[EMAIL PROTECTED]>
Cc: "Mod-perl list" <[EMAIL PROTECTED]>
Sent: Monday, June 17, 2002 6:37 PM
Subject: Re: custom directives, again...


> At 00:25 18.06.2002, Noam Solomon wrote:
> >Thanks -- that got me over one hurdle!  Next one:
> >
> >Syntax error on line 382 of /home/build/httpd/server/./conf/httpd.conf:
> >Invalid command 'AddIconByEncoding', perhaps mis-spelled or defined by a
> >module not included in the server configuration
> >I've replaced the startup.pl call with:
> >
> >   #PerlModule Apache::AutoIndex
> >   PerlModule Apache::OpenIndex
> >   PerlModule Apache::Icon
> >   PerlModule Apache::AuthCookie
> >Switching on AutoIndex versus OpenIndex makes no difference.
> >
> >Any idea what could be going on here?  I just tried reinstalling
> >Apache::Icon, with
> >no improvement.
>
> Sorry, I'm at a loss here.
>
> >
> >Thanks

Re: custom directives, again...

[darren chamberlain]

* Noam Solomon <[EMAIL PROTECTED]> [2002-06-17 17:49]:
> I sent out a plea for help last week, but probably didn't provide
> enough information for a quick solution. The problem is that I'm using
> Apache::OpenIndex (which is similar to Apache::AutoIndex) and have not
> been able to get the apache server on the production box to detect a
> custom directive it defines (OpenIndexOptions). I didn't have this
> problem on my development machine, so I'm baffled as to its origin.

[-- snip --]

> Here's some salient bits of the httpd.conf:
> 
>   # GLOBAL MOD_PERL CONFIG
>   
> AddModule mod_perl.c
> PerlRequire /home/httpd/startup.pl
> PerlFreshRestart On
> etc..
> PerlRequire /home/httpd/mason/handler.pl
>   
>   # END GLOBAL MOD_PERL CONFIG

Make sure that you pull in the module using PerlModule, and not from use
in a PerlRequire.  PerlModule does some bootstrapping to make sure that
directives are passed to your module, rather than let Apache try to do
something with them.

(darren)

-- 
Make no laws whatever concerning speech, and speech will be free;
so soon as you make a declaration on paper that speech shall be
free, you will have a hundred lawyers proving that "freedom does
not mean abuse, nor liberty license"; and they will define and
define freedom out of existence.
-- Voltarine de Cleyre