NYCPHP Meetup

[Jeff Slutz]

I've also run into the "headers already sent" sort of issue being caused by
line breaks or white space after a closing php marker "?>".  This is
considered output to the screen and then any following php header()
commands will fail.

--
Jeff Slutz
JSLEUTH LLC
2105 N Fork Drive
Lafayette, CO 80026
c. 970.443.9390
jeff at jeffslutz.com


On Fri, Sep 27, 2013 at 10:38 AM, Ajai Khattri <ajai at bitblit.net> wrote:

> On Fri, Sep 27, 2013 at 10:04:53AM -0400, Tedd Sperling wrote:
>
> > 1. The error "headers already sent " is created when you have already
> sent stuff to the browser and try to do it again. Functions that
> send/modify HTTP headers must be invoked before any output is made.
> Otherwise the call fails.
>
> Could also be caused by errors generating output - so check your web
> server error logs.
>
>
> --
> Aj.
> FaceBook: facebook.com/ajaikhattri
> EnoLand: http://flip.it/Gig0n
> _______________________________________________
> New York PHP User Group Community Talk Mailing List
> http://lists.nyphp.org/mailman/listinfo/talk
>
> http://www.nyphp.org/show-participation
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nyphp.org/pipermail/talk/attachments/20130927/4502c324/attachment.html>