Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #17288
Show key headers only | View raw
Jerry Stuckle <jstucklex@attglobal.net> writes: > On 1/13/2017 3:35 PM, the well-known troll Thomas 'Pointed Head' Lahn wrote: >> Christoph M. Becker wrote: >> >>> On 13.01.2017 at 19:30, wart2ww wrote: >>>> On Friday, January 13, 2017 at 9:58:27 AM UTC-8, Jerry Stuckle wrote: >>>>> The fact you're getting the message indicates you are outputting >>>>> something before the header call. You should also have a message >>>>> indicating what line on which file is generating the output. >>>> >>>> I will keep trying. FYI, I did put the php block at the top of the page >>>> above any html (before the doctype declaration, made sure there were not >>>> spaces before the php block and even put the entire header code on one >>>> line with no spaces then with some spaces in the statement. Still no >>>> success so that what confuses me. I won't bug you any more but I really >>>> do appreciate your help. >>> >>> As Jerry had written, the message you get is something like >>> >>> "Cannot send headers; headers already sent in <filename>, line >>> <lineno> in <filename>:<lineno>" >>> >>> The last <filename> and <lineno> indicate the place of the header() >>> call, the first <filename> and <lineno> indicate where the output started. >> >> Another common reason for this problem is that the used source code editor >> prepends an (if supported, invisible) byte order mark (BOM; usually, for >> UTF-8 encoded source code). AFAIK, the BOM can be shown with a hex editor >> (or equivalent, like “cat -A”), or an unsupporting text editor (rare these >> days) only. >> >> For example, the first octets of PHP source code with an UTF-8 BOM can look >> in a hex editor [here: Pascal 'Pixel' Rigaux’ hexedit(1)] as follows: >> >> | 00000000 EF BB BF 3C 3F 70 68 70 … ...<?php… >> >> An editor that does not support UTF-8 could display “” for the BOM, >> because those are the characters at the code points 0xEF, 0xBB, and 0xBF in >> ISO/IEC-8859-1 (“Latin alphabet no. 1” or “Latin-1”) for short, and >> Windows-1252/CP-1252 (”Western”). >> >> <https://en.wikipedia.org/wiki/ISO/IEC_8859-1#Codepage_layout> >> >> For PHP source code, the source code editor has to be configured so that >> it does not prepend a BOM, or another editor has to be used for final >> storage; otherwise it is impossible to avoid the warning and the problem. >> >> <https://en.wikipedia.org/wiki/Byte_order_mark> > > Which I mentioned a couple of days ago. Do you ever post something > original? Thomas Lahn and I hardly see eye to eye on anything, but his post clearly contains original material: an possible explanation of how this may have come about (the editor); some advice on further debugging the issue (a hex editor or cat -A); and he clears up a misconception the OP might have taken from your remark that "you can't use UTF-8 or any other charset which has a BOM". -- Ben.
Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Problem validating user and hashed value in db wart2ww <fcc@bmi.net> - 2017-01-10 12:46 -0800
Re: Problem validating user and hashed value in db Jerry Stuckle <jstucklex@attglobal.net> - 2017-01-10 22:39 -0500
Re: Problem validating user and hashed value in db wart2ww <fcc@bmi.net> - 2017-01-10 19:51 -0800
Re: Problem validating user and hashed value in db Jerry Stuckle <jstucklex@attglobal.net> - 2017-01-10 23:28 -0500
Re: Problem validating user and hashed value in db wart2ww <fcc@bmi.net> - 2017-01-10 22:32 -0800
Re: Problem validating user and hashed value in db "Christoph M. Becker" <cmbecker69@arcor.de> - 2017-01-11 12:47 +0100
Re: Problem validating user and hashed value in db Jerry Stuckle <jstucklex@attglobal.net> - 2017-01-11 09:07 -0500
Re: Problem validating user and hashed value in db "Christoph M. Becker" <cmbecker69@arcor.de> - 2017-01-11 15:37 +0100
Re: Problem validating user and hashed value in db Jerry Stuckle <jstucklex@attglobal.net> - 2017-01-11 15:40 -0500
Re: Problem validating user and hashed value in db Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2017-01-11 23:18 +0100
Re: Problem validating user and hashed value in db wart2ww <fcc@bmi.net> - 2017-01-12 07:32 -0800
Re: Problem validating user and hashed value in db "Christoph M. Becker" <cmbecker69@arcor.de> - 2017-01-12 17:23 +0100
Re: Problem validating user and hashed value in db wart2ww <fcc@bmi.net> - 2017-01-12 10:18 -0800
Re: Problem validating user and hashed value in db "Christoph M. Becker" <cmbecker69@arcor.de> - 2017-01-12 19:36 +0100
Re: Problem validating user and hashed value in db wart2ww <fcc@bmi.net> - 2017-01-12 11:12 -0800
Re: Problem validating user and hashed value in db wart2ww <fcc@bmi.net> - 2017-01-12 12:05 -0800
Re: Problem validating user and hashed value in db Jerry Stuckle <jstucklex@attglobal.net> - 2017-01-12 15:20 -0500
Re: Problem validating user and hashed value in db wart2ww <fcc@bmi.net> - 2017-01-12 13:51 -0800
Re: Problem validating user and hashed value in db Jerry Stuckle <jstucklex@attglobal.net> - 2017-01-12 17:00 -0500
Re: Problem validating user and hashed value in db wart2ww <fcc@bmi.net> - 2017-01-12 13:53 -0800
Re: Problem validating user and hashed value in db Jerry Stuckle <jstucklex@attglobal.net> - 2017-01-12 17:02 -0500
Re: Problem validating user and hashed value in db wart2ww <fcc@bmi.net> - 2017-01-13 07:16 -0800
Re: Problem validating user and hashed value in db Jerry Stuckle <jstucklex@attglobal.net> - 2017-01-13 10:39 -0500
Re: Problem validating user and hashed value in db wart2ww <fcc@bmi.net> - 2017-01-13 09:06 -0800
Re: Problem validating user and hashed value in db Jerry Stuckle <jstucklex@attglobal.net> - 2017-01-13 12:58 -0500
Re: Problem validating user and hashed value in db wart2ww <fcc@bmi.net> - 2017-01-13 10:30 -0800
Re: Problem validating user and hashed value in db Jerry Stuckle <jstucklex@attglobal.net> - 2017-01-13 13:57 -0500
Re: Problem validating user and hashed value in db wart2ww <fcc@bmi.net> - 2017-01-13 13:29 -0800
Re: Problem validating user and hashed value in db Jerry Stuckle <jstucklex@attglobal.net> - 2017-01-13 16:57 -0500
Re: Problem validating user and hashed value in db wart2ww <fcc@bmi.net> - 2017-01-13 14:23 -0800
Re: Problem validating user and hashed value in db Jerry Stuckle <jstucklex@attglobal.net> - 2017-01-14 13:03 -0500
Re: Problem validating user and hashed value in db "Christoph M. Becker" <cmbecker69@arcor.de> - 2017-01-13 20:02 +0100
Re: Problem validating user and hashed value in db Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2017-01-13 21:35 +0100
Re: Problem validating user and hashed value in db Jerry Stuckle <jstucklex@attglobal.net> - 2017-01-13 16:24 -0500
Re: Problem validating user and hashed value in db Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-01-14 02:37 +0000
Re: Problem validating user and hashed value in db wart2ww <fcc@bmi.net> - 2017-01-13 19:20 -0800
Re: Problem validating user and hashed value in db Jerry Stuckle <jstucklex@attglobal.net> - 2017-01-14 12:57 -0500
Re: Problem validating user and hashed value in db Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2017-01-14 19:47 +0100
Re: Problem validating user and hashed value in db Jerry Stuckle <jstucklex@attglobal.net> - 2017-01-14 14:00 -0500
Re: Problem validating user and hashed value in db Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2017-01-13 16:27 +0100
Re: Problem validating user and hashed value in db "Christoph M. Becker" <cmbecker69@arcor.de> - 2017-01-13 16:39 +0100
Re: Problem validating user and hashed value in db Jerry Stuckle <jstucklex@attglobal.net> - 2017-01-11 09:22 -0500
csiph-web