| PHP Always Outputs [message #178624] |
Sat, 14 July 2012 04:21  |
Ryan
Messages: 15
Registered: July 2012
Karma: 0
|
Junior Member |
|
|
I want a php script to run and simply output nothing. But even this script:
<?php
?>
will output this html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=windows-1252" http-equiv=Content-Type></HEAD>
<BODY></BODY></HTML>
Is there a setting somewhere in my php or apache config that needs to be turned off?
|
|
|
|
| Re: PHP Always Outputs [message #178625 is a reply to message #178624] |
Sat, 14 July 2012 08:54  |
Luuk
Messages: 329
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 14-07-2012 06:21, Ryan wrote:
> I want a php script to run and simply output nothing. But even this script:
>
> <?php
> ?>
>
> will output this html
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <HTML><HEAD>
> <META content="text/html; charset=windows-1252" http-equiv=Content-Type></HEAD>
> <BODY></BODY></HTML>
>
> Is there a setting somewhere in my php or apache config that needs to be turned off?
>
no, PHP will not output what you said.
The output you see is generated by apache.....
~/tmp> cat empty.php
<?php
?>
~/tmp> php -f empty.php
~/tmp>
|
|
|
|
| Re: PHP Always Outputs [message #178626 is a reply to message #178624] |
Sat, 14 July 2012 13:17 |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 7/14/2012 12:21 AM, Ryan wrote:
> I want a php script to run and simply output nothing. But even this script:
>
> <?php
> ?>
>
> will output this html
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <HTML><HEAD>
> <META content="text/html; charset=windows-1252" http-equiv=Content-Type></HEAD>
> <BODY></BODY></HTML>
>
> Is there a setting somewhere in my php or apache config that needs to be turned off?
>
No, it doesn't. The PHP code you showed will only generate the
appropriate response headers - no HTML.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|
|
| Re: PHP Always Outputs [message #178627 is a reply to message #178625] |
Sat, 14 July 2012 13:19 |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 7/14/2012 4:54 AM, Luuk wrote:
> On 14-07-2012 06:21, Ryan wrote:
>> I want a php script to run and simply output nothing. But even this script:
>>
>> <?php
>> ?>
>>
>> will output this html
>>
>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
>> <HTML><HEAD>
>> <META content="text/html; charset=windows-1252" http-equiv=Content-Type></HEAD>
>> <BODY></BODY></HTML>
>>
>> Is there a setting somewhere in my php or apache config that needs to be turned off?
>>
>
> no, PHP will not output what you said.
>
> The output you see is generated by apache.....
>
> ~/tmp> cat empty.php
> <?php
> ?>
> ~/tmp> php -f empty.php
> ~/tmp>
>
>
No, Apache does not generate HTML.
Additionally, PHP generates different output (the appropriate response
headers) when run as module or CGI than when run as a CLI. But it will
not generate HTML on its own.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|
|
| Re: PHP Always Outputs [message #178628 is a reply to message #178624] |
Sat, 14 July 2012 13:37 |
Doug Miller
Messages: 171
Registered: August 2011
Karma: 0
|
Senior Member |
|
|
Ryan <rbilesky(at)gmail(dot)com> wrote in news:a5baa7aa-287c-4862-8ab9-898783d691f4
@googlegroups.com:
> I want a php script to run and simply output nothing. But even this script:
>
> <?php
> ?>
>
> will output this html
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <HTML><HEAD>
> <META content="text/html; charset=windows-1252" http-equiv=Content-Type></HEAD>
> <BODY></BODY></HTML>
>
> Is there a setting somewhere in my php or apache config that needs to be turned off?
Check your .htaccess file -- it probably contains a line that looks like this:
php_value auto_prepend_file "foo.php"
with the contents of the file foo.php resembling
echo "!<DOCTYPE HTML PUBLIC...";
echo "<HTML><HEAD>";
etc.
|
|
|
|
| Re: PHP Always Outputs [message #178629 is a reply to message #178628] |
Sat, 14 July 2012 13:46 |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 7/14/2012 9:37 AM, Doug Miller wrote:
> Ryan <rbilesky(at)gmail(dot)com> wrote in news:a5baa7aa-287c-4862-8ab9-898783d691f4
> @googlegroups.com:
>
>> I want a php script to run and simply output nothing. But even this script:
>>
>> <?php
>> ?>
>>
>> will output this html
>>
>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
>> <HTML><HEAD>
>> <META content="text/html; charset=windows-1252" http-equiv=Content-Type></HEAD>
>> <BODY></BODY></HTML>
>>
>> Is there a setting somewhere in my php or apache config that needs to be turned off?
>
> Check your .htaccess file -- it probably contains a line that looks like this:
>
> php_value auto_prepend_file "foo.php"
>
> with the contents of the file foo.php resembling
>
> echo "!<DOCTYPE HTML PUBLIC...";
> echo "<HTML><HEAD>";
> etc.
>
If it were, it would be seriously broken. There would be no way to add
<HEAD> tags or the <BODY> in their proper places.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|
|
| Re: PHP Always Outputs [message #178630 is a reply to message #178627] |
Sat, 14 July 2012 14:21 |
Luuk
Messages: 329
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 14-07-2012 15:19, Jerry Stuckle wrote:
> On 7/14/2012 4:54 AM, Luuk wrote:
>> On 14-07-2012 06:21, Ryan wrote:
>>> I want a php script to run and simply output nothing. But even this
>>> script:
>>>
>>> <?php
>>> ?>
>>>
>>> will output this html
>>>
>>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
>>> <HTML><HEAD>
>>> <META content="text/html; charset=windows-1252"
>>> http-equiv=Content-Type></HEAD>
>>> <BODY></BODY></HTML>
>>>
>>> Is there a setting somewhere in my php or apache config that needs to
>>> be turned off?
>>>
>>
>> no, PHP will not output what you said.
>>
>> The output you see is generated by apache.....
>>
>> ~/tmp> cat empty.php
>> <?php
>> ?>
>> ~/tmp> php -f empty.php
>> ~/tmp>
>>
>>
>
> No, Apache does not generate HTML.
>
> Additionally, PHP generates different output (the appropriate response
> headers) when run as module or CGI than when run as a CLI. But it will
> not generate HTML on its own.
>
you are right
~/tmp> vi ../public_html/empty.php
~/tmp> wget -S "http://www.example.com/~luuk/empty.php" -O output.txt
asking libproxy about url 'http://www.example.com/~luuk/empty.php'
libproxy suggest to use 'direct://'
--2012-07-14 16:18:07-- http://www.example.com/~luuk/empty.php
Resolving www.example.com (www.example.com)... 192.168.178.250
Connecting to www.example.com (www.example.com)|192.168.178.250|:80...
connected.
HTTP request sent, awaiting response...
HTTP/1.1 200 OK
Date: Sat, 14 Jul 2012 14:18:07 GMT
Server: Apache/2.2.21 (Linux/SUSE)
X-Powered-By: PHP/5.3.8
Content-Length: 0
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html
Length: 0 [text/html]
Saving to: `output.txt'
[ <=>
] 0 --.-K/s in 0s
2012-07-14 16:18:07 (0.00 B/s) - `output.txt' saved [0/0]
Legnth is 0 bytes, so i'm sure no one is interested in the output.... ;)
|
|
|
|
| Re: PHP Always Outputs [message #178631 is a reply to message #178629] |
Sat, 14 July 2012 14:40 |
Doug Miller
Messages: 171
Registered: August 2011
Karma: 0
|
Senior Member |
|
|
Jerry Stuckle <jstucklex(at)attglobal(dot)net> wrote in
news:jtrt6u$ccj$1(at)dont-email(dot)me:
> On 7/14/2012 9:37 AM, Doug Miller wrote:
>> Ryan <rbilesky(at)gmail(dot)com> wrote in
>> news:a5baa7aa-287c-4862-8ab9-898783d691f4 @googlegroups.com:
>>
>>> I want a php script to run and simply output nothing. But
>>> even this script:
>>>
>>> <?php
>>> ?>
>>>
>>> will output this html
>>>
>>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
>>> <HTML><HEAD>
>>> <META content="text/html; charset=windows-1252"
>>> http-equiv=Content-Type></HEAD> <BODY></BODY></HTML>
>>>
>>> Is there a setting somewhere in my php or apache config that
>>> needs to be turned off?
>>
>> Check your .htaccess file -- it probably contains a line that
>> looks like this:
>>
>> php_value auto_prepend_file "foo.php"
>>
>> with the contents of the file foo.php resembling
>>
>> echo "!<DOCTYPE HTML PUBLIC...";
>> echo "<HTML><HEAD>";
>> etc.
>>
> If it were, it would be seriously broken.
I disagree.
> There would be no way
> to add <HEAD> tags or the <BODY> in their proper places.
Of course there is. I have reproduced the OP's results *exactly*
with the following:
C:\WebSites\fubar>type .htaccess
php_value auto_prepend_file "prepend.php"
php_value auto_append_file "append.txt"
C:\WebSites\fubar>type prepend.php
<?php
printf ("<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.0 Transitional//EN\">\n");
printf ("<HTML><HEAD>\n");
printf ("<META content=\"text/html; charset=windows-1252\" http-equiv=Content-Type>
</HEAD>\n");
printf ("<BODY>");
?>
C:\WebSites\fubar>type append.txt
</BODY></HTML>
Content of the OP's pages will be served between the <BODY> and </BODY> tags. If he
wants to be able to add tags in the HEAD section as well, it's simple enough to insert
readfile ("head_tags.txt")
into the file prepend.php somewhere between <HEAD> and <\HEAD>, putting the desired
tags into head_tags.txt.
|
|
|
|
| Re: PHP Always Outputs [message #178632 is a reply to message #178630] |
Sat, 14 July 2012 14:51 |
Luuk
Messages: 329
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 14-07-2012 16:21, Luuk wrote:
> On 14-07-2012 15:19, Jerry Stuckle wrote:
>> On 7/14/2012 4:54 AM, Luuk wrote:
>>> On 14-07-2012 06:21, Ryan wrote:
>>>> I want a php script to run and simply output nothing. But even this
>>>> script:
>>>>
>>>> <?php
>>>> ?>
>>>>
>>>> will output this html
>>>>
>>>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
>>>> <HTML><HEAD>
>>>> <META content="text/html; charset=windows-1252"
>>>> http-equiv=Content-Type></HEAD>
>>>> <BODY></BODY></HTML>
>>>>
>>>> Is there a setting somewhere in my php or apache config that needs to
>>>> be turned off?
>>>>
>>>
>>> no, PHP will not output what you said.
>>>
>>> The output you see is generated by apache.....
>>>
>>> ~/tmp> cat empty.php
>>> <?php
>>> ?>
>>> ~/tmp> php -f empty.php
>>> ~/tmp>
>>>
>>>
>>
>> No, Apache does not generate HTML.
oops, i should have typed:
The output you see is 'problably' generated by apache?.....
>>
>> Additionally, PHP generates different output (the appropriate response
>> headers) when run as module or CGI than when run as a CLI. But it will
>> not generate HTML on its own.
so, in this case PHP will not output anyythingm
>>
>
>
> ~/tmp> vi ../public_html/empty.php
> ~/tmp> wget -S "http://www.example.com/~luuk/empty.php" -O output.txt
> asking libproxy about url 'http://www.example.com/~luuk/empty.php'
> libproxy suggest to use 'direct://'
> --2012-07-14 16:18:07-- http://www.example.com/~luuk/empty.php
> Resolving www.example.com (www.example.com)... 192.168.178.250
> Connecting to www.example.com (www.example.com)|192.168.178.250|:80...
> connected.
> HTTP request sent, awaiting response...
> HTTP/1.1 200 OK
> Date: Sat, 14 Jul 2012 14:18:07 GMT
> Server: Apache/2.2.21 (Linux/SUSE)
> X-Powered-By: PHP/5.3.8
> Content-Length: 0
> Keep-Alive: timeout=15, max=100
> Connection: Keep-Alive
> Content-Type: text/html
> Length: 0 [text/html]
> Saving to: `output.txt'
>
> [ <=>
> ] 0 --.-K/s in 0s
>
> 2012-07-14 16:18:07 (0.00 B/s) - `output.txt' saved [0/0]
>
>
> Legnth is 0 bytes, so i'm sure no one is interested in the output.... ;)
>
remains the question from the OP
if PHP does not do it (as proved above),
i'm sure someone will say:
"This output is not caused by PHP, so 'ask somewhere else'"
@Ryan:
where did you see this:"<!DOCTYPE HTML PUBLIC....."
Did you start Internet Explorer, and looked at 'view source'???????
In that case, the HTML was created by IE
--
Luuk
|
|
|
|
| Re: PHP Always Outputs [message #178633 is a reply to message #178631] |
Sat, 14 July 2012 19:00 |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 7/14/2012 10:40 AM, Doug Miller wrote:
> Jerry Stuckle <jstucklex(at)attglobal(dot)net> wrote in
> news:jtrt6u$ccj$1(at)dont-email(dot)me:
>
>> On 7/14/2012 9:37 AM, Doug Miller wrote:
>>> Ryan <rbilesky(at)gmail(dot)com> wrote in
>>> news:a5baa7aa-287c-4862-8ab9-898783d691f4 @googlegroups.com:
>>>
>>>> I want a php script to run and simply output nothing. But
>>>> even this script:
>>>>
>>>> <?php
>>>> ?>
>>>>
>>>> will output this html
>>>>
>>>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
>>>> <HTML><HEAD>
>>>> <META content="text/html; charset=windows-1252"
>>>> http-equiv=Content-Type></HEAD> <BODY></BODY></HTML>
>>>>
>>>> Is there a setting somewhere in my php or apache config that
>>>> needs to be turned off?
>>>
>>> Check your .htaccess file -- it probably contains a line that
>>> looks like this:
>>>
>>> php_value auto_prepend_file "foo.php"
>>>
>>> with the contents of the file foo.php resembling
>>>
>>> echo "!<DOCTYPE HTML PUBLIC...";
>>> echo "<HTML><HEAD>";
>>> etc.
>>>
>> If it were, it would be seriously broken.
>
> I disagree.
>
>> There would be no way
>> to add <HEAD> tags or the <BODY> in their proper places.
>
> Of course there is. I have reproduced the OP's results *exactly*
> with the following:
>
> C:\WebSites\fubar>type .htaccess
> php_value auto_prepend_file "prepend.php"
> php_value auto_append_file "append.txt"
>
>
> C:\WebSites\fubar>type prepend.php
> <?php
> printf ("<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.0 Transitional//EN\">\n");
> printf ("<HTML><HEAD>\n");
> printf ("<META content=\"text/html; charset=windows-1252\" http-equiv=Content-Type>
> </HEAD>\n");
> printf ("<BODY>");
> ?>
>
> C:\WebSites\fubar>type append.txt
> </BODY></HTML>
>
> Content of the OP's pages will be served between the <BODY> and </BODY> tags. If he
> wants to be able to add tags in the HEAD section as well, it's simple enough to insert
> readfile ("head_tags.txt")
> into the file prepend.php somewhere between <HEAD> and <\HEAD>, putting the desired
> tags into head_tags.txt.
>
Now, how is the user supposed to place other <HEAD> tags such as
<TITLE>, <SCRIPT> and <LINK>? The answer is, he can't. And while he
*could* put a readfile() in there, it would be no different than placing
the tags directly in the file. He couldn't customize the tags to the page.
While what you say *could* be used - it would result in a seriously
broken site with the inability to add such tags.
Also, there would be no need to use printf() there. Just the HTML code
itself would be fine.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|
|
| Re: PHP Always Outputs [message #178634 is a reply to message #178632] |
Sat, 14 July 2012 19:46 |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 7/14/2012 10:51 AM, Luuk wrote:
> On 14-07-2012 16:21, Luuk wrote:
>> On 14-07-2012 15:19, Jerry Stuckle wrote:
>>> On 7/14/2012 4:54 AM, Luuk wrote:
>>>> On 14-07-2012 06:21, Ryan wrote:
>>>> > I want a php script to run and simply output nothing. But even this
>>>> > script:
>>>> >
>>>> > <?php
>>>> > ?>
>>>> >
>>>> > will output this html
>>>> >
>>>> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
>>>> > <HTML><HEAD>
>>>> > <META content="text/html; charset=windows-1252"
>>>> > http-equiv=Content-Type></HEAD>
>>>> > <BODY></BODY></HTML>
>>>> >
>>>> > Is there a setting somewhere in my php or apache config that needs to
>>>> > be turned off?
>>>> >
>>>>
>>>> no, PHP will not output what you said.
>>>>
>>>> The output you see is generated by apache.....
>>>>
>>>> ~/tmp> cat empty.php
>>>> <?php
>>>> ?>
>>>> ~/tmp> php -f empty.php
>>>> ~/tmp>
>>>>
>>>>
>>>
>>> No, Apache does not generate HTML.
>
> oops, i should have typed:
> The output you see is 'problably' generated by apache?.....
>
>
>>>
>>> Additionally, PHP generates different output (the appropriate response
>>> headers) when run as module or CGI than when run as a CLI. But it will
>>> not generate HTML on its own.
>
> so, in this case PHP will not output anyythingm
>
>>>
>>
>>
>> ~/tmp> vi ../public_html/empty.php
>> ~/tmp> wget -S "http://www.example.com/~luuk/empty.php" -O output.txt
>> asking libproxy about url 'http://www.example.com/~luuk/empty.php'
>> libproxy suggest to use 'direct://'
>> --2012-07-14 16:18:07-- http://www.example.com/~luuk/empty.php
>> Resolving www.example.com (www.example.com)... 192.168.178.250
>> Connecting to www.example.com (www.example.com)|192.168.178.250|:80...
>> connected.
>> HTTP request sent, awaiting response...
>> HTTP/1.1 200 OK
>> Date: Sat, 14 Jul 2012 14:18:07 GMT
>> Server: Apache/2.2.21 (Linux/SUSE)
>> X-Powered-By: PHP/5.3.8
>> Content-Length: 0
>> Keep-Alive: timeout=15, max=100
>> Connection: Keep-Alive
>> Content-Type: text/html
>> Length: 0 [text/html]
>> Saving to: `output.txt'
>>
>> [ <=>
>> ] 0 --.-K/s in 0s
>>
>> 2012-07-14 16:18:07 (0.00 B/s) - `output.txt' saved [0/0]
>>
>>
>> Legnth is 0 bytes, so i'm sure no one is interested in the output.... ;)
>>
>
> remains the question from the OP
>
> if PHP does not do it (as proved above),
> i'm sure someone will say:
> "This output is not caused by PHP, so 'ask somewhere else'"
>
> @Ryan:
>
> where did you see this:"<!DOCTYPE HTML PUBLIC....."
> Did you start Internet Explorer, and looked at 'view source'???????
> In that case, the HTML was created by IE
>
Yes, he's using IE, which inserted the HTML when it got a blank page
back. This can easily be duplicated in IE 8.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|
|
| Re: PHP Always Outputs [message #178635 is a reply to message #178633] |
Sat, 14 July 2012 20:12 |
Doug Miller
Messages: 171
Registered: August 2011
Karma: 0
|
Senior Member |
|
|
Jerry Stuckle <jstucklex(at)attglobal(dot)net> wrote in
news:jtsfl7$rqo$1(at)dont-email(dot)me:
> On 7/14/2012 10:40 AM, Doug Miller wrote:
>> Jerry Stuckle <jstucklex(at)attglobal(dot)net> wrote in
>> news:jtrt6u$ccj$1(at)dont-email(dot)me:
>>
>>> On 7/14/2012 9:37 AM, Doug Miller wrote:
>>>> Ryan <rbilesky(at)gmail(dot)com> wrote in
>>>> news:a5baa7aa-287c-4862-8ab9-898783d691f4 @googlegroups.com:
>>>>
>>>> > I want a php script to run and simply output nothing. But
>>>> > even this script:
>>>> >
>>>> > <?php
>>>> > ?>
>>>> >
>>>> > will output this html
>>>> >
>>>> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
>>>> > Transitional//EN"> <HTML><HEAD>
>>>> > <META content="text/html; charset=windows-1252"
>>>> > http-equiv=Content-Type></HEAD> <BODY></BODY></HTML>
>>>> >
>>>> > Is there a setting somewhere in my php or apache config that
>>>> > needs to be turned off?
>>>>
>>>> Check your .htaccess file -- it probably contains a line that
>>>> looks like this:
>>>>
>>>> php_value auto_prepend_file "foo.php"
>>>>
>>>> with the contents of the file foo.php resembling
>>>>
>>>> echo "!<DOCTYPE HTML PUBLIC...";
>>>> echo "<HTML><HEAD>";
>>>> etc.
>>>>
>>> If it were, it would be seriously broken.
>>
>> I disagree.
>>
>>> There would be no way
>>> to add <HEAD> tags or the <BODY> in their proper places.
>>
>> Of course there is. I have reproduced the OP's results
>> *exactly* with the following:
>>
>> C:\WebSites\fubar>type .htaccess
>> php_value auto_prepend_file "prepend.php"
>> php_value auto_append_file "append.txt"
>>
>>
>> C:\WebSites\fubar>type prepend.php
>> <?php
>> printf ("<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.0
>> Transitional//EN\">\n"); printf ("<HTML><HEAD>\n");
>> printf ("<META content=\"text/html; charset=windows-1252\"
>> http-equiv=Content-Type> </HEAD>\n");
>> printf ("<BODY>");
>> ?>
>>
>> C:\WebSites\fubar>type append.txt
>> </BODY></HTML>
>>
>> Content of the OP's pages will be served between the <BODY> and
>> </BODY> tags. If he wants to be able to add tags in the HEAD
>> section as well, it's simple enough to insert readfile
>> ("head_tags.txt") into the file prepend.php somewhere between
>> <HEAD> and <\HEAD>, putting the desired tags into
>> head_tags.txt.
>>
>
> Now, how is the user supposed to place other <HEAD> tags such as
> <TITLE>, <SCRIPT> and <LINK>? The answer is, he can't.
Ummmm, yes, he can. I just described how that can be done.
> And while he
> *could* put a readfile() in there, it would be no different than
> placing the tags directly in the file. He couldn't customize
> the tags to the page.
I didn't say that the tags could be customized. But you *did* say
they couldn't be inserted at all. Which they obviously can.
>
> While what you say *could* be used - it would result in a
> seriously broken site with the inability to add such tags.
Again -- there is no such "inability to add" tags in the HEAD
section. OK, they can't be customized. But let's back up a few
paragraphs, to where you said "there would be no way" to add them.
Of course there is.
> Also, there would be no need to use printf() there. Just the
> HTML code itself would be fine.
If the prepended file is just HTML code, not a PHP script, then
it's not possible to use readfile() to insert any head tags that
may be desired.
|
|
|
|
| Re: PHP Always Outputs [message #178636 is a reply to message #178635] |
Sat, 14 July 2012 20:16 |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 7/14/2012 4:12 PM, Doug Miller wrote:
> Jerry Stuckle <jstucklex(at)attglobal(dot)net> wrote in
> news:jtsfl7$rqo$1(at)dont-email(dot)me:
>
>> On 7/14/2012 10:40 AM, Doug Miller wrote:
>>> Jerry Stuckle <jstucklex(at)attglobal(dot)net> wrote in
>>> news:jtrt6u$ccj$1(at)dont-email(dot)me:
>>>
>>>> On 7/14/2012 9:37 AM, Doug Miller wrote:
>>>> > Ryan <rbilesky(at)gmail(dot)com> wrote in
>>>> > news:a5baa7aa-287c-4862-8ab9-898783d691f4 @googlegroups.com:
>>>> >
>>>> >> I want a php script to run and simply output nothing. But
>>>> >> even this script:
>>>> >>
>>>> >> <?php
>>>> >> ?>
>>>> >>
>>>> >> will output this html
>>>> >>
>>>> >> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
>>>> >> Transitional//EN"> <HTML><HEAD>
>>>> >> <META content="text/html; charset=windows-1252"
>>>> >> http-equiv=Content-Type></HEAD> <BODY></BODY></HTML>
>>>> >>
>>>> >> Is there a setting somewhere in my php or apache config that
>>>> >> needs to be turned off?
>>>> >
>>>> > Check your .htaccess file -- it probably contains a line that
>>>> > looks like this:
>>>> >
>>>> > php_value auto_prepend_file "foo.php"
>>>> >
>>>> > with the contents of the file foo.php resembling
>>>> >
>>>> > echo "!<DOCTYPE HTML PUBLIC...";
>>>> > echo "<HTML><HEAD>";
>>>> > etc.
>>>> >
>>>> If it were, it would be seriously broken.
>>>
>>> I disagree.
>>>
>>>> There would be no way
>>>> to add <HEAD> tags or the <BODY> in their proper places.
>>>
>>> Of course there is. I have reproduced the OP's results
>>> *exactly* with the following:
>>>
>>> C:\WebSites\fubar>type .htaccess
>>> php_value auto_prepend_file "prepend.php"
>>> php_value auto_append_file "append.txt"
>>>
>>>
>>> C:\WebSites\fubar>type prepend.php
>>> <?php
>>> printf ("<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.0
>>> Transitional//EN\">\n"); printf ("<HTML><HEAD>\n");
>>> printf ("<META content=\"text/html; charset=windows-1252\"
>>> http-equiv=Content-Type> </HEAD>\n");
>>> printf ("<BODY>");
>>> ?>
>>>
>>> C:\WebSites\fubar>type append.txt
>>> </BODY></HTML>
>>>
>>> Content of the OP's pages will be served between the <BODY> and
>>> </BODY> tags. If he wants to be able to add tags in the HEAD
>>> section as well, it's simple enough to insert readfile
>>> ("head_tags.txt") into the file prepend.php somewhere between
>>> <HEAD> and <\HEAD>, putting the desired tags into
>>> head_tags.txt.
>>>
>>
>> Now, how is the user supposed to place other <HEAD> tags such as
>> <TITLE>, <SCRIPT> and <LINK>? The answer is, he can't.
>
> Ummmm, yes, he can. I just described how that can be done.
>
>> And while he
>> *could* put a readfile() in there, it would be no different than
>> placing the tags directly in the file. He couldn't customize
>> the tags to the page.
>
> I didn't say that the tags could be customized. But you *did* say
> they couldn't be inserted at all. Which they obviously can.
That is not inserting tags. It is just copying them from a file - just
as if they were in the original header.
>>
>> While what you say *could* be used - it would result in a
>> seriously broken site with the inability to add such tags.
>
> Again -- there is no such "inability to add" tags in the HEAD
> section. OK, they can't be customized. But let's back up a few
> paragraphs, to where you said "there would be no way" to add them.
> Of course there is.
>
Which makes them pretty worthless. And no, you are NOT "adding them".
You are just placing fixed tags in the header.
>> Also, there would be no need to use printf() there. Just the
>> HTML code itself would be fine.
>
> If the prepended file is just HTML code, not a PHP script, then
> it's not possible to use readfile() to insert any head tags that
> may be desired.
>
Which, since it is always reading the same file, is no different than
just placing the tags in the HTML file itself.
You are over-complicating the problem with a *very stoopid* response.
The *real* problem here is that IE is inserting the HTML when it gets
the blank page back. It is easily duplicated in IE8.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|
|
| Re: PHP Always Outputs [message #178637 is a reply to message #178636] |
Sun, 15 July 2012 00:59 |
Doug Miller
Messages: 171
Registered: August 2011
Karma: 0
|
Senior Member |
|
|
Jerry Stuckle <jstucklex(at)attglobal(dot)net> wrote in news:jtsk27$lrt$1(at)dont-email(dot)me:
> You are over-complicating the problem with a *very stoopid* response.
Typical Jerry -- proven wrong (once again), you resort to insults (once again).
> The *real* problem here is that IE is inserting the HTML when it gets
> the blank page back. It is easily duplicated in IE8.
I wouldn't know -- I haven't used IE for years, and don't plan to start.
|
|
|
|
| Re: PHP Always Outputs [message #178638 is a reply to message #178637] |
Sun, 15 July 2012 01:49 |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 7/14/2012 8:59 PM, Doug Miller wrote:
> Jerry Stuckle <jstucklex(at)attglobal(dot)net> wrote in news:jtsk27$lrt$1(at)dont-email(dot)me:
>
>> You are over-complicating the problem with a *very stoopid* response.
>
> Typical Jerry -- proven wrong (once again), you resort to insults (once again).
>
>> The *real* problem here is that IE is inserting the HTML when it gets
>> the blank page back. It is easily duplicated in IE8.
>
> I wouldn't know -- I haven't used IE for years, and don't plan to start.
>
>
Nope, you're so stoopid you don't see how asinine (and wrong) your
"response" is. But you still try to defend it! (It isn't working).
And you claim I'm "wrong" - but refuse to run the simple test I shows
you that proves it.
Just another example of you trolling.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|
|
| Re: PHP Always Outputs [message #178650 is a reply to message #178638] |
Sun, 15 July 2012 16:14 |
Doug Miller
Messages: 171
Registered: August 2011
Karma: 0
|
Senior Member |
|
|
Jerry Stuckle <jstucklex(at)attglobal(dot)net> wrote in news:jtt7jb$tj6$1(at)dont-email(dot)me:
> On 7/14/2012 8:59 PM, Doug Miller wrote:
>> Jerry Stuckle <jstucklex(at)attglobal(dot)net> wrote in news:jtsk27$lrt$1(at)dont-email(dot)me:
>>
>>> You are over-complicating the problem with a *very stoopid* response.
>>
>> Typical Jerry -- proven wrong (once again), you resort to insults (once again).
>>
>>> The *real* problem here is that IE is inserting the HTML when it gets
>>> the blank page back. It is easily duplicated in IE8.
>>
>> I wouldn't know -- I haven't used IE for years, and don't plan to start.
>>
>>
>
> Nope, you're so stoopid you don't see how asinine (and wrong) your
> "response" is. But you still try to defend it! (It isn't working).
I never claimed it was the only, or even the best, explanation of what the OP observed, only
that it was a *possible* explanation.
> And you claim I'm "wrong" - but refuse to run the simple test I shows
> you that proves it.
I already ran the test that proves you wrong. I don't need to run *another* one.
>
> Just another example of you trolling.
>
Just another example of your typical behavior. One thing is different this time, though: this
time, I've had enough of your obnoxious, immature behavior. This is long overdue, but
better late than never: I'm killfiling you, Jerry, so don't bother responding. I won't see it.
|
|
|
|
| Re: PHP Always Outputs [message #178652 is a reply to message #178650] |
Sun, 15 July 2012 18:15 |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 7/15/2012 12:14 PM, Doug Miller wrote:
> Jerry Stuckle <jstucklex(at)attglobal(dot)net> wrote in news:jtt7jb$tj6$1(at)dont-email(dot)me:
>
>> On 7/14/2012 8:59 PM, Doug Miller wrote:
>>> Jerry Stuckle <jstucklex(at)attglobal(dot)net> wrote in news:jtsk27$lrt$1(at)dont-email(dot)me:
>>>
>>>> You are over-complicating the problem with a *very stoopid* response.
>>>
>>> Typical Jerry -- proven wrong (once again), you resort to insults (once again).
>>>
>>>> The *real* problem here is that IE is inserting the HTML when it gets
>>>> the blank page back. It is easily duplicated in IE8.
>>>
>>> I wouldn't know -- I haven't used IE for years, and don't plan to start.
>>>
>>>
>>
>> Nope, you're so stoopid you don't see how asinine (and wrong) your
>> "response" is. But you still try to defend it! (It isn't working).
>
> I never claimed it was the only, or even the best, explanation of what the OP observed, only
> that it was a *possible* explanation.
>
>> And you claim I'm "wrong" - but refuse to run the simple test I shows
>> you that proves it.
>
> I already ran the test that proves you wrong. I don't need to run *another* one.
>>
>> Just another example of you trolling.
>>
> Just another example of your typical behavior. One thing is different this time, though: this
> time, I've had enough of your obnoxious, immature behavior. This is long overdue, but
> better late than never: I'm killfiling you, Jerry, so don't bother responding. I won't see it.
>
Ah, another troll can't handle the truth!
Good riddance, Doug. I just wish you'd get out of the group all
together. It would be a much nicer place.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|
|
| Re: PHP Always Outputs [message #178657 is a reply to message #178624] |
Mon, 16 July 2012 09:52 |
alvaro.NOSPAMTHANX
Messages: 277
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
El 14/07/2012 6:21, Ryan escribió/wrote:
> I want a php script to run and simply output nothing. But even this script:
>
> <?php
> ?>
>
> will output this html
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <HTML><HEAD>
> <META content="text/html; charset=windows-1252" http-equiv=Content-Type></HEAD>
> <BODY></BODY></HTML>
>
> Is there a setting somewhere in my php or apache config that needs to be turned off?
Apparently, you are inspecting the output through a web browser and your
browser has reached the conclusion that you are loading an HTML
document. Since your (empty) code is not valid HTML, the browser does
what it's been designed to do: fix it. In this case, it adds a few tags
to obtain a valid empty HTML document.
The PHP way to make sure your output is not handled as HTML is to send
an appropriate HTTP header, e.g.:
header('Content-Type: text/plain');
Additionally, you can remove the trailing "?>" closing tag, which is not
mandatory and might lead to white space being sent to the browser.
The use of uppercase tags and Win-1252 encoding suggests we are talking
about Internet Explorer. This browser is known for ignoring the
Content-Type under certain circumstances. But of course that's another
story.
--
-- http://alvaro.es - Álvaro G. Vicario - Burgos, Spain
-- Mi sitio sobre programación web: http://borrame.com
-- Mi web de humor satinado: http://www.demogracia.com
--
|
|
|
|
| Re: PHP Always Outputs [message #178660 is a reply to message #178624] |
Mon, 16 July 2012 12:20 |
Arno Welzel
Messages: 317
Registered: October 2011
Karma: 0
|
Senior Member |
|
|
Am 14.07.2012 06:21, schrieb Ryan:
> I want a php script to run and simply output nothing. But even this script:
>
> <?php
> ?>
>
> will output this html
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <HTML><HEAD>
> <META content="text/html; charset=windows-1252" http-equiv=Content-Type></HEAD>
> <BODY></BODY></HTML>
It may be your client which automatically creates this for "empty"
documents. Did you verify this using wget or similar?
As you can see here - <http://arnowelzel.de/samples/empty.php> - this
script does not produce any output.
--
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de
|
|
|
|
| Re: PHP Always Outputs [message #178667 is a reply to message #178657] |
Mon, 16 July 2012 18:18 |
Tim Streater
Messages: 328
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
In article <ju0o9o$6dt$1(at)dont-email(dot)me>,
"Álvaro G. Vicario" <alvaro(dot)NOSPAMTHANX(at)demogracia(dot)com(dot)invalid> wrote:
> El 14/07/2012 6:21, Ryan escribió/wrote:
>> I want a php script to run and simply output nothing. But even this
>> script:
>>
>> <?php
>> ?>
>>
>> will output this html
>>
>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
>> <HTML><HEAD>
>> <META content="text/html; charset=windows-1252"
>> http-equiv=Content-Type></HEAD>
>> <BODY></BODY></HTML>
>>
>> Is there a setting somewhere in my php or apache config that needs to be
>> turned off?
>
> Apparently, you are inspecting the output through a web browser and your
> browser has reached the conclusion that you are loading an HTML
> document. Since your (empty) code is not valid HTML, the browser does
> what it's been designed to do: fix it. In this case, it adds a few tags
> to obtain a valid empty HTML document.
>
> The PHP way to make sure your output is not handled as HTML is to send
> an appropriate HTTP header, e.g.:
>
> header('Content-Type: text/plain');
header ('Content-Type: text/plain; charset=utf-8');
is better.
--
Tim
"That excessive bail ought not to be required, nor excessive fines imposed,
nor cruel and unusual punishments inflicted" -- Bill of Rights 1689
|
|
|
|
| Re: PHP Always Outputs [message #178669 is a reply to message #178650] |
Mon, 16 July 2012 23:48 |
Michael Vilain
Messages: 88
Registered: September 2010
Karma: 0
|
Member |
|
|
In article <XnsA0917C7126E6Ddougmilmaccom(at)88(dot)198(dot)244(dot)100>,
Doug Miller <doug_at_milmac_dot_com(at)example(dot)com> wrote:
> Jerry Stuckle <jstucklex(at)attglobal(dot)net> wrote in
> news:jtt7jb$tj6$1(at)dont-email(dot)me:
>
>>
>> Just another example of you trolling.
>>
> Just another example of your typical behavior. One thing is different this
> time, though: this
> time, I've had enough of your obnoxious, immature behavior. This is long
> overdue, but
> better late than never: I'm killfiling you, Jerry, so don't bother
> responding. I won't see it.
I gave up listening to Jerry and his twaddle years ago. So far, he
hasn't kept silent long enough to expire from my killfile so I'm
guessing when he finally does, he'll either be in Assisted Care and
barred from the Day Room computers or dead. I'm voting for #2,
personally.
--
DeeDee, don't press that button! DeeDee! NO! Dee...
[I filter all Goggle Groups posts, so any reply may be automatically ignored]
|
|
|
|
| Re: PHP Always Outputs [message #178670 is a reply to message #178669] |
Tue, 17 July 2012 00:30 |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 7/16/2012 7:48 PM, Michael Vilain wrote:
> In article <XnsA0917C7126E6Ddougmilmaccom(at)88(dot)198(dot)244(dot)100>,
> Doug Miller <doug_at_milmac_dot_com(at)example(dot)com> wrote:
>
>> Jerry Stuckle <jstucklex(at)attglobal(dot)net> wrote in
>> news:jtt7jb$tj6$1(at)dont-email(dot)me:
>>
>>>
>>> Just another example of you trolling.
>>>
>> Just another example of your typical behavior. One thing is different this
>> time, though: this
>> time, I've had enough of your obnoxious, immature behavior. This is long
>> overdue, but
>> better late than never: I'm killfiling you, Jerry, so don't bother
>> responding. I won't see it.
>
> I gave up listening to Jerry and his twaddle years ago. So far, he
> hasn't kept silent long enough to expire from my killfile so I'm
> guessing when he finally does, he'll either be in Assisted Care and
> barred from the Day Room computers or dead. I'm voting for #2,
> personally.
>
I really don't give a damn if you don't want to learn how to do things
correctly. It's your loss, not mine.
And chances are I'll end up with more of your clients than you will of mine.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|
|
|
|
| Re: PHP Always Outputs [message #178679 is a reply to message #178669] |
Tue, 17 July 2012 08:12 |
The Natural Philosoph
Messages: 993
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
Michael Vilain wrote:
> In article <XnsA0917C7126E6Ddougmilmaccom(at)88(dot)198(dot)244(dot)100>,
> Doug Miller <doug_at_milmac_dot_com(at)example(dot)com> wrote:
>
>> Jerry Stuckle <jstucklex(at)attglobal(dot)net> wrote in
>> news:jtt7jb$tj6$1(at)dont-email(dot)me:
>>
>>> Just another example of you trolling.
>>>
>> Just another example of your typical behavior. One thing is different this
>> time, though: this
>> time, I've had enough of your obnoxious, immature behavior. This is long
>> overdue, but
>> better late than never: I'm killfiling you, Jerry, so don't bother
>> responding. I won't see it.
>
> I gave up listening to Jerry and his twaddle years ago. So far, he
> hasn't kept silent long enough to expire from my killfile so I'm
> guessing when he finally does, he'll either be in Assisted Care and
> barred from the Day Room computers or dead. I'm voting for #2,
> personally.
>
+1
--
To people who know nothing, anything is possible.
To people who know too much, it is a sad fact
that they know how little is really possible -
and how hard it is to achieve it.
|
|
|
|
| Re: PHP Always Outputs [message #178683 is a reply to message #178677] |
Tue, 17 July 2012 08:49 |
Tim Streater
Messages: 328
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
In article <ju34au$aem$1(at)dont-email(dot)me>,
"Álvaro G. Vicario" <alvaro(dot)NOSPAMTHANX(at)demogracia(dot)com(dot)invalid> wrote:
> El 16/07/2012 20:18, Tim Streater escribió/wrote:
>>> header('Content-Type: text/plain');
>>
>> header ('Content-Type: text/plain; charset=utf-8');
>>
>> is better.
>
> To display an empty file?
I can do *that* by opening a new document in TextWrangler. But if I want
to do something useful using SQLite, PHP, ajax, JavaScript, CSS, and
HTML, I eventually figured out that using utf-8 throughout made my life
a lot easier. Especially as I can convert any junk I receive *into*
utf-8, using PHP tools.
--
Tim
"That excessive bail ought not to be required, nor excessive fines imposed,
nor cruel and unusual punishments inflicted" -- Bill of Rights 1689
|
|
|
|
| Re: PHP Always Outputs [message #178684 is a reply to message #178683] |
Tue, 17 July 2012 09:03 |
M. Strobel
Messages: 386
Registered: December 2011
Karma: 0
|
Senior Member |
|
|
Am 17.07.2012 10:49, schrieb Tim Streater:
> In article <ju34au$aem$1(at)dont-email(dot)me>,
> "Álvaro G. Vicario" <alvaro(dot)NOSPAMTHANX(at)demogracia(dot)com(dot)invalid> wrote:
>
>> El 16/07/2012 20:18, Tim Streater escribió/wrote:
>>>> header('Content-Type: text/plain');
>>>
>>> header ('Content-Type: text/plain; charset=utf-8');
>>>
>>> is better.
>>
>> To display an empty file?
>
> I can do *that* by opening a new document in TextWrangler. But if I want to do
> something useful using SQLite, PHP, ajax, JavaScript, CSS, and HTML, I eventually
> figured out that using utf-8 throughout made my life a lot easier. Especially as I
> can convert any junk I receive *into* utf-8, using PHP tools.
>
Of course AGV is making fun of the charset for an empty file, but apart from that I
wish the use of utf-8 were generally accepted. I just don't understand why there is
still so much iso-8859 in use, this charset is so limited.
/Str.
|
|
|
|
| Re: PHP Always Outputs [message #178695 is a reply to message #178684] |
Tue, 17 July 2012 14:58 |
Peter H. Coffin
Messages: 245
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On Tue, 17 Jul 2012 11:03:31 +0200, M. Strobel wrote:
> Am 17.07.2012 10:49, schrieb Tim Streater:
>
>> In article <ju34au$aem$1(at)dont-email(dot)me>, "??lvaro G. Vicario"
>> <alvaro(dot)NOSPAMTHANX(at)demogracia(dot)com(dot)invalid> wrote:
>>
>>> El 16/07/2012 20:18, Tim Streater escribi??/wrote:
>>>
>>>> > header('Content-Type: text/plain');
>>>>
>>>> header ('Content-Type: text/plain; charset=utf-8');
>>>>
>>>> is better.
>>>
>>> To display an empty file?
>>
>> I can do *that* by opening a new document in TextWrangler. But if I
>> want to do something useful using SQLite, PHP, ajax, JavaScript, CSS,
>> and HTML, I eventually figured out that using utf-8 throughout made
>> my life a lot easier. Especially as I can convert any junk I receive
>> *into* utf-8, using PHP tools.
>
> Of course AGV is making fun of the charset for an empty file, but
> apart from that I wish the use of utf-8 were generally accepted. I
> just don't understand why there is still so much iso-8859 in use, this
> charset is so limited.
Inertia and lack of awareness.
--
_ o
|/)
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]