Apache2 reveals SOURCE of PHP!

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • JZ

    Apache2 reveals SOURCE of PHP!

    Had anybody problems with the newest PHP and Apache?

    I have compiled from sources Apache 2.0.48 and PHP 4.3.4. For Apache
    --with-mpm=worker option was used. I was using Linux RedHat 9
    (2xXeon2.8GHz. 3GB RAM) PHP was used as the module of Apache (not
    CGI).

    The problem is: that SOMETIMES (sic!) PHP pages are not parsed at all
    and Apache reveals their SOURCE CODE! But sometimes, the same page is
    parsed and everything looks OK. Do you have any idea, what is going on
    there?

    --
    JZ
  • CountScubula

    #2
    Re: Apache2 reveals SOURCE of PHP!

    "JZ" <jroznfgre@jngp ugbjreQBGbet.cy > wrote in message
    news:1a15vv4gdn hlveoeqdjta3hev 74vok4ht0@4ax.c om...[color=blue]
    > Had anybody problems with the newest PHP and Apache?
    >
    > I have compiled from sources Apache 2.0.48 and PHP 4.3.4. For Apache
    > --with-mpm=worker option was used. I was using Linux RedHat 9
    > (2xXeon2.8GHz. 3GB RAM) PHP was used as the module of Apache (not
    > CGI).
    >
    > The problem is: that SOMETIMES (sic!) PHP pages are not parsed at all
    > and Apache reveals their SOURCE CODE! But sometimes, the same page is
    > parsed and everything looks OK. Do you have any idea, what is going on
    > there?
    >
    > --
    > JZ[/color]

    Is there any distiction of when this happens/doesnot happen?

    file extentions? folders? domains? time of day? full moon? leap year?

    --
    Mike Bradley
    http://gzen.myhq.info -- free online php tools


    Comment

    • JZ

      #3
      Re: Apache2 reveals SOURCE of PHP!

      On Wed, 31 Dec 2003 08:25:14 GMT, "CountScubu la"
      <me@scantek.hot mail.com> wrote:
      [color=blue]
      >"JZ" <jroznfgre@jngp ugbjreQBGbet.cy > wrote in message
      >news:1a15vv4gd nhlveoeqdjta3he v74vok4ht0@4ax. com...[color=green]
      >> Had anybody problems with the newest PHP and Apache?
      >>
      >> I have compiled from sources Apache 2.0.48 and PHP 4.3.4. For Apache
      >> --with-mpm=worker option was used. I was using Linux RedHat 9
      >> (2xXeon2.8GHz. 3GB RAM) PHP was used as the module of Apache (not
      >> CGI).
      >>
      >> The problem is: that SOMETIMES (sic!) PHP pages are not parsed at all
      >> and Apache reveals their SOURCE CODE! But sometimes, the same page is
      >> parsed and everything looks OK. Do you have any idea, what is going on
      >> there?[/color]
      >
      >Is there any distiction of when this happens/doesnot happen?
      >
      >file extentions? folders? domains? time of day? full moon? leap year?[/color]

      No, not at all. When I reload the same page several times, sometimes
      it is parsed, simetimes not, and I can see php source.

      --
      JZ

      Comment

      • CountScubula

        #4
        Re: Apache2 reveals SOURCE of PHP!

        Ok, u got me on this one, but I will continue to ponder over it, it is
        bugging me, becouse I saw this once before while I was surfing around.
        Would be nice to know answer

        --
        Mike Bradley
        http://gzen.myhq.info -- free online php tools
        "JZ" <jroznfgre@jngp ugbjreQBGbet.cy > wrote in message
        news:7635vvc4np jnorqrqd5qiutus h9f23shq6@4ax.c om...[color=blue]
        > On Wed, 31 Dec 2003 08:25:14 GMT, "CountScubu la"
        > <me@scantek.hot mail.com> wrote:
        >[color=green]
        > >"JZ" <jroznfgre@jngp ugbjreQBGbet.cy > wrote in message
        > >news:1a15vv4gd nhlveoeqdjta3he v74vok4ht0@4ax. com...[color=darkred]
        > >> Had anybody problems with the newest PHP and Apache?
        > >>
        > >> I have compiled from sources Apache 2.0.48 and PHP 4.3.4. For Apache
        > >> --with-mpm=worker option was used. I was using Linux RedHat 9
        > >> (2xXeon2.8GHz. 3GB RAM) PHP was used as the module of Apache (not
        > >> CGI).
        > >>
        > >> The problem is: that SOMETIMES (sic!) PHP pages are not parsed at all
        > >> and Apache reveals their SOURCE CODE! But sometimes, the same page is
        > >> parsed and everything looks OK. Do you have any idea, what is going on
        > >> there?[/color]
        > >
        > >Is there any distiction of when this happens/doesnot happen?
        > >
        > >file extentions? folders? domains? time of day? full moon? leap year?[/color]
        >
        > No, not at all. When I reload the same page several times, sometimes
        > it is parsed, simetimes not, and I can see php source.
        >
        > --
        > JZ[/color]


        Comment

        • Larry

          #5
          Re: Apache2 reveals SOURCE of PHP!

          CountScubula wrote:
          [color=blue]
          > Ok, u got me on this one, but I will continue to ponder over it, it is
          > bugging me, becouse I saw this once before while I was surfing around.
          > Would be nice to know answer
          >[/color]

          Could it be a server performance issue?

          --

          Comment

          • CountScubula

            #6
            Re: Apache2 reveals SOURCE of PHP!

            "Larry" <sorry@butnoema il.com> wrote in message
            news:MvCdnWpmxe BXnW6iRVn-vw@comcast.com. ..[color=blue]
            > CountScubula wrote:
            >[color=green]
            > > Ok, u got me on this one, but I will continue to ponder over it, it is
            > > bugging me, becouse I saw this once before while I was surfing around.
            > > Would be nice to know answer
            > >[/color]
            >
            > Could it be a server performance issue?
            >
            > --
            > www.eSnider.net[/color]


            Thought about that a bit, but what I don't get is if apache is set to filter
            it (either through zend or php) then it must be filtered, it doesn't change
            its mind and sometimes filter. Or I could be wrong?

            I have been searching for any post anywhere with anything to do with this,
            have found anything on an intermitit problem.

            --
            Mike Bradley
            http://gzen.myhq.info -- free online php tools


            Comment

            • Larry

              #7
              Re: Apache2 reveals SOURCE of PHP!

              CountScubula wrote:
              [color=blue]
              > "Larry" <sorry@butnoema il.com> wrote in message[color=green]
              >> Could it be a server performance issue?[/color][/color]
              [color=blue]
              > Thought about that a bit, but what I don't get is if apache is set to
              > filter it (either through zend or php) then it must be filtered, it
              > doesn't change its mind and sometimes filter. Or I could be wrong?[/color]

              I wouldn't think so unless the filter is messed up.

              --

              Comment

              • JZ

                #8
                Re: Apache2 reveals SOURCE of PHP!

                On Wed, 31 Dec 2003 09:27:10 GMT, "CountScubu la"
                <me@scantek.hot mail.com> wrote:
                [color=blue]
                >Ok, u got me on this one, but I will continue to ponder over it, it is
                >bugging me, becouse I saw this once before while I was surfing around.
                >Would be nice to know answer[/color]

                Check those:



                --
                JZ

                Comment

                • Joshua Beall

                  #9
                  Re: Apache2 reveals SOURCE of PHP!

                  "JZ" <jroznfgre@jngp ugbjreQBGbet.cy > wrote in message
                  news:1a15vv4gdn hlveoeqdjta3hev 74vok4ht0@4ax.c om...[color=blue]
                  > SOMETIMES (sic!) PHP pages are not parsed at all
                  > and Apache reveals their SOURCE CODE![/color]

                  Whoa, that is not good... can you post examples of this behavior? I have
                  not seen this happen, although I have seen Apache 2 work fine.


                  Comment

                  Working...