Hi Toby:
Yes, that's the way I did, but it's not so clean, you have to open each time you
write!
--
Saludos, Rubén Blanco.
__
A r t e k - 928.52.20.77 - http://www.artek.es
>> >One thing that occurs to me -- stdout starts off by bein
Hi Dotan:
PHP Version 4.0.1pl2
Ruben.
>> I actually was getting prompted to download the .php file sometimes...
>
>So, the user would be able to open the file in, say, VI and see your code? Big
>>security
>hole, no? Of which versions of php4 was this characteristic?
>
>Dotan Cohen
>--
> >One thing that occurs to me -- stdout starts off by being
the browser, so
> >it's kinda funky to open it -- You've already got it
open... I *think* it
> >really only makes sense to fopen() stdout from the
command line. At least,
> >I'm not clear on what it would mean to open it from a
HTTP en
> I actually was getting prompted to download the .php file sometimes...
So, the user would be able to open the file in, say, VI and see your code? Big
security hole, no? Of which versions of php4 was this characteristic?
Dotan Cohen
---
MySQLphp4
Hi Richard, thank you for your answer:
>> When calling the php4 code below, sometimes the browser receives
>> -the "HTML estandar text"
>> -sometimes the "Text generated from PHP" (but NEVER both!)
>> -and ocassionaly the error:
>> "Warning: fopen("php://stdout","w") - Bad file descriptor in
>> /
> When calling the php4 code below, sometimes the browser receives
> -the "HTML estandar text"
> -sometimes the "Text generated from PHP" (but NEVER both!)
> -and ocassionaly the error:
> "Warning: fopen("php://stdout","w") - Bad file descriptor in
> /home/sites/site74/web/_proc/pruebas/stdout-tes
Hi!
When calling the php4 code below, sometimes the browser receives
-the "HTML estandar text"
-sometimes the "Text generated from PHP" (but NEVER both!)
-and ocassionaly the error:
"Warning: fopen("php://stdout","w") - Bad file descriptor in
/home/sites/site74/web/_proc/pruebas/stdout-test.php
7 matches
Mail list logo