NYCPHP Meetup

[Chris Shiflett]

I heard that PHP has always been notorious for sometimes not  
processing requests poorly and sending back the source code for pages  
to the client:

http://shiflett.org/blog/2007/sep/catching-up-and-keeping-up

It's a shame that guy's blog no longer exists. At least the TechCrunch  
story still does. :-)

Chris

On Dec 1, 2008, at 22:07, Justin Dearing wrote:

> Michele,
>
> I think your ISP lied to you. Assuming its apache and mod_php I'm  
> pretty sure that the only explanation was they reconfigured apache  
> wrong, restarted apache, you saw the issue, reported it, and they  
> fixed it.
>
> If your server is a windows server (unlikely in a shared hosting  
> senario) or this is something like lighthttpd or php running on  
> apache through some configuration I'm not totatly familiar with like  
> CGI, then maybe this can happen.
>
> If what you experienced is a common occurrence with mod_php, I hope  
> others on this list will chime in. If it is I'm going to cease using  
> apache and mod_php in production environments.
>
>
> On Mon, Dec 1, 2008 at 9:51 PM, Michele Waldman  
> <mmwaldman at nyc.rr.com> wrote:
> I'm not sure which process died, but I was programming one night and  
> all of the sudden all of my php code was being dumped to my browser.
>
> I called my hosting provider and they said the underlying process  
> had died for some reason.
>

--
Chris Shiflett
http://shiflett.org/