Re: [PHP] Re: PHP and Jigsaw
>Some careful testing and results... I know nothing about Jigsaw, whatever that is. >All tests invoke the URL "http://myserver:jigsawport/phpinfo.php"; > >Test 1: >* phpinfo.php contains exactly one line > > >* Jigsaw's debug flag in the default extension indexer cgiframe definition >for ".php" files is "true". > >The browser shows a white page with the text: >X-Powered-By: PHP/4.2.1 >Content-type: text/html > >Invoking the "view->source" menu path launches a notepad session showing >exactly the same text as the browser with NO html tags. PHP *IS* being invoked, and *IS* starting to send its output to the browser. PHP *might* be mis-configured somehow so that a blank line is getting sent before its header output, or Jigsaw might be adding a blank line before PHP's output, but *SOMETHING* is forcing a blank line into the HTTP stream that comes to the browser *before* those headers arrive. That's just wrong. Can you completely remove jigsaw from the equation? Not just setting some flag to true/false, but be 100% sure jigsaw isn't even running? >Test 2. >* phpinfo.php contains exactly one line > > >* Jigsaw's debug flag is "false". > >The browser shows an empty white page. > >Invoking the "view->source" menu path launches a notepad session showing the >following: > > > > Okay, then we know for sure that jigsaw "true" is messing up your headers. Possibly with an ERROR message and a blank line. The browser swallows the error message as a header, and then display's PHP's output headers as if it were content. Can you run jigsaw from the MS-DOS prompt or command line or whatever, feeding it the same PHP URL somehow? >Test 3. >* phpinfo.php now contains some trivial container html. > >phpinfo page > >phpinfo follows... > > > > >* Jigsaw's debug flag is "false". > >The browser shows an empty white page. > >Invoking the "view->source" menu path launches a notepad session showing the >following: > > > > Well, yes, this isn't PHP's output, almost for sure. I dunno who or what is sending this junk out, but it's probably not PHP. >The DOS prompt running Jigsaw has the process name "JAVA" until the php page >is invoked. At this time it is renamed to php and stays that way. The >Jigsaw server, however, does still respond to JigAdmin commands and can be >stopped correctly. > >Ummm When php.exe fires up, apparently using the same MS-DOS shell as jigsaw, it renames the window title. That's normal. If you take Jigsaw out of the picture, and manage to watch the MS-DOS window that runs PHP fire up and then quite (minimize your browser and hit 'reload') then you'd see that happen, maybe... Make PHP do a and you'll have 10 seconds to read it. :-) If you can get rid of Jigsaw and make sure PHP works without it, you can pretty safely assume it's Jigsaw that is messing up, somehow. If you can "feed" Jigsaw the same output PHP sends it, and see what it does without a browser getting in the way, you'll probably see an error message that tells you something useful. Well, "useful" here is relative :-) -- Like Music? http://l-i-e.com/artists.htm -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Re: PHP and Jigsaw
Some careful testing and results... All tests invoke the URL "http://myserver:jigsawport/phpinfo.php"; Test 1: * phpinfo.php contains exactly one line * Jigsaw's debug flag in the default extension indexer cgiframe definition for ".php" files is "true". The browser shows a white page with the text: X-Powered-By: PHP/4.2.1 Content-type: text/html Invoking the "view->source" menu path launches a notepad session showing exactly the same text as the browser with NO html tags. Test 2. * phpinfo.php contains exactly one line * Jigsaw's debug flag is "false". The browser shows an empty white page. Invoking the "view->source" menu path launches a notepad session showing the following: Test 3. * phpinfo.php now contains some trivial container html. phpinfo page phpinfo follows... * Jigsaw's debug flag is "false". The browser shows an empty white page. Invoking the "view->source" menu path launches a notepad session showing the following: The DOS prompt running Jigsaw has the process name "JAVA" until the php page is invoked. At this time it is renamed to php and stays that way. The Jigsaw server, however, does still respond to JigAdmin commands and can be stopped correctly. Ummm Murray Nicholas -Original Message- From: Richard Lynch [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 16 July 2002 15:13 To: [EMAIL PROTECTED] Subject: [PHP] Re: PHP and Jigsaw >With Jigsaw's debug facility Enabled, I get two lines on the page and the >same two lines (without html tags of any sort) in "view source" display: >X-Powered-By: PHP/4.2.1 >Content-type: text/html If these two lines are showing up in the BROWSER, then something is pretty wrong... They're supposed to be headers... So something could be sending out a blank line or something before these, somehow... If they are just showing up in debugging output, and they *ARE* headers, then PHP *IS* getting invoked, and then dying when it tries to execute your code. Try using *JUST* this in your PHP document: It's pretty hard to screw up something that short, so you'll know the PHP is valid :-) And, if it works, you get a wonderfully long HTML document spewed out. It's so fun to type so little and get so much :-) -- Like Music? http://l-i-e.com/artists.htm -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Re: PHP and Jigsaw
>With Jigsaw's debug facility Enabled, I get two lines on the page and the >same two lines (without html tags of any sort) in "view source" display: >X-Powered-By: PHP/4.2.1 >Content-type: text/html If these two lines are showing up in the BROWSER, then something is pretty wrong... They're supposed to be headers... So something could be sending out a blank line or something before these, somehow... If they are just showing up in debugging output, and they *ARE* headers, then PHP *IS* getting invoked, and then dying when it tries to execute your code. Try using *JUST* this in your PHP document: It's pretty hard to screw up something that short, so you'll know the PHP is valid :-) And, if it works, you get a wonderfully long HTML document spewed out. It's so fun to type so little and get so much :-) -- Like Music? http://l-i-e.com/artists.htm -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
