Well, I will try again...

I just noticed the "Valid file extensions" thingy. It is now called "httpd.txt" so it might let me upload it...

--daveo

    Hi,

    where are the two include statements for the files php.conf and perl.conf ? Are they located at the position where you inserted them in you posted text file ? Try to move the includes somewhere after the "standard" LoadModule directives or to the end of httpd.conf.

      Hi,

      two more ideas:

      1) I read some posts about mod_perl preventing apache to load the php module.

      Try the following:

      First load just the two modules mod_perl and mod_php4. Then put all the perl and php configuration stuff below the two LoadModule lines.

      2) configure apache to use php as cgi.

        Ok. 3 ideas:

        1st/2nd: It appears that ideas 1 and 2 are similar, basically, LoadModule everything first that do the extra config stuff at the bottom (near the VirtualHost stuff). Correct me if this is wrong.

        3rd: do all else normally except setting up PHP as cgi. Is there something other than setting the ScriptAlias, AddType and Action directives?

        I think I tried as cgi before and got the same results. I say "think I tried" because I don't know if things were in the right order or not. :o

        I will try these suggestions shortly. Any guidance that you want to give on the 'cgi' part would be nice since you are currently on-line. I will, most likely, be trying these after the kids are in bed. 🙂

        Thanks again for all so far...

        --daveo

          Hi,

          I think it would be better to get the stuff working with the so version of php 🙂

          What happened with php when you tried to deactivate the mod_perl stuff ? Did it work ?

          I found a url yesterday where someone described how he compiled apache2, php-4.3.0, mod_perl,mod_ssl and other stuff, I'll look where it was and send you the url. If it worked for him, why shouldn't it work for you ? I think he was running RedHat 8.0 🙂

            Hi,

            the person wasn't using RedHat 8.0 but it should work anyways:
            It's a nice step by stell tutorial and includes ssl stuff (and shows how to create a self signed certificate)

            http://lamps.efactory.de/e-lamps-2-0.shtml

            By the way, I read another post of someone who wrote that for him using the mpm switch when compiling apache broke up the php execution. Try to recompile apache without

            --with-mpm=prefork

            I must say that I don't have RedHat 8.0 installed yet but I think I'll go and get it 🙂

              I'm slowly working through that guy's document and, consequently, adding PDF and a signed certificate to the mix 🆒.

              As it turns out, the default for Linux is

              "--with-mpm=prefork"

              so if you leave that line out, it defaults to it. Just for kicks, I tried

              "--without-mpm"

              and (as I suspected from reading the docs) you can't do that. mpm is what talks to the network ports. Ya learn something new every day (if you are lucky). 🙂

              Anyway, I am still working at it. More later.

              --daveo

                In the words of the infamous Valley Girls (and guys?) of California: "Oh my Gawd!".

                First: I have it working (loud fanfare) and can break (and fix) it easily.

                Second: order of directives has "a little" to do with it; but, only the order of PHP directives, however, are at issue. The rest can go in the "conf.d/*.conf" files as suggested by the Apache2 sample httpd.conf.

                The one "extra element" that you are probably not using is "Apache::ASP" (http://www.apache-asp.org/). That "stuff" isn't the real source of the problem, but the "Files" directive that I was using turned out to be a killer!

                See if you can explain this behavior:

                With the "Files" section as follows:

                <Files ~ (.asp)?>
                ... some settings ...
                </Files>

                With that setup, PHP will not work but the Perl ASP scripts do. When I change it to:

                <Files ~ (.asp)$>
                ... some settings ...
                </Files>

                BOTH Apache::ASP and PHP stuff work. Now, mind you, the PHP setup was:

                <Files ~ (.php)?>
                ... some settings ...
                </Files>

                and that caused no problems.

                By the way, I have no idea why the "?" was in the ".asp" Files directive, but it was...

                Any ideas?

                I will wait to see if anyone has any ideas on this before closing out this thread. The answer(s) could be interesting/useful.

                --daveo

                  Hi,

                  I think the ? after the brackets means 0,1 so all files that ended with .asp and all file that didn't end with .asp matched so all files matched. By using $ you match all files that exactly end with .asp. I would suggest to use (.php)$ instead of (.php)? because it would render all files sections after the php section useless.

                    Ummmm... yeah. That was pretty silly on my part. Especially since I am the one who has to explain regexps to all my co-workers.

                    For some reason, there was a

                    <Brain>
                    Mode=slow
                    </Brain>

                    section in the file near that part. I had been thinking (or, more accurately, NOT thinking) that it would match the "?" in the URL for parameters.

                    Thank-you for your patience in helping on this one.

                      Closing Summary:

                      1) Order can be important
                      2) Watch those FilesMatch and Files directives.

                      1) The order of my directives was important, possibly because I had another <Files> directive that was too general, I will have to investigate that.

                      2) my PHP scripts were not being seen because the

                      <Files ~ (.asp)?>

                      directive was grabbing them and passing them to Apache::ASP (which passed them along as simple text). The correct syntax should have been:

                      <Files ~ ".asp$">

                      which would have found files ending in ".asp".

                      --daveo

                        Write a Reply...