p2p.wrox.com Forums

Need to download code?

View our list of code downloads.


  Return to Index  

beginning_php thread: RE: problem with using headers to prevent - - cachein- g


Message #1 by IT_KTS@P... on Wed, 4 Jul 2001 09:20:29

SOMEONE SAID THAT PHP IS DESIGNED AS A HIGH LEVEL LANGUAGE, TRUE... I USED 

HEADER() MORE OFTEN WHETHER THERE IS A NEW LINE OR NOT AND IT DOES'NT 

MATTER, IT STILL WORKS.. OF COURSE BEFORE PASSING ANY HTML CODE..



SO I THINK IS YOU BETTER GO ON WITH YOUR LIVES NOW.. AND CONTINUE YOUR 

PROJECT.., etc.. 







> Everything you want to know about HTTP is in this document:

> http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc2068.html

> 

> 

> > Referring back to an earlier question raised in this thread, someone 

has

> > yet to offer an explanation as to why space before header statements

> > should prompt the error messages (quoted once more below), which if 

taken

> > literally, suggest that space is header information and therefore 

deemed

> > as sent before reading the real header information?

> >

> >   "Warning: Cannot add header information - headers already sent by

> >   (output started at c:\phpweb/test.php:2) in c:\phpweb/test.php on 

line 3

> >

> >   Warning: Cannot add header information - headers already sent by

> >   (output started at c:\phpweb/test.php:2) in c:\phpweb/test.php on 

line 4

> >

> >   Warning: Cannot add header information - headers already sent by

> >   (output started at c:\phpweb/test.php:2) in c:\phpweb/test.php on 

line 5"

> >

> > Another question: what is the 'output' in these messages?

> 


  Return to Index