ID: 8311
Updated by: sas
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Closed
Bug Type: *Session related
Assigned To: 
Comments:

(I assume you are using the transparent session ID propagation feature.)

This issue has been addressed in PHP 4.0.4.  An upgrade to the latest version should 
cure the problem.

Previous Comments:
---------------------------------------------------------------------------

[2001-01-19 20:22:59] [EMAIL PROTECTED]
reclassifying.
BTW, this is not IIS-specific, it has been reported for Mandrake too (#8686).

---------------------------------------------------------------------------

[2000-12-18 07:00:37] [EMAIL PROTECTED]
using IIS 5.0 and php4.0.3pl1 as an ISAPI module;

referring to bug ID #8271:

the problem does not seem to be related to the "include()" statement...

I have some code generating a clientside java script to generate a form input (tested 
wit hand without the include stuff):

   print " document.writeln("<input type=\"checkbox\" ...>");";

including the session_start() statement generates the following code:

   document.writeln("<input type="""checkbox" ... >");

resulting in a browser error...

comment the session_start() out and the code looks like:

   document.writeln("<input type="checkbox" ... >");

as should be...


Second test:

print " document.writeln("<input type=checkbox ...>");";

including the session_start() statement generates the following code:

   document.writeln("<input type="checkbox" ... >");

resulting in a browser error...

comment the session_start() out and the code looks like:

   document.writeln("<input type=checkbox ... >");

as should be...


The problem does not occurr when hosting the page on Linux/Apache...

Regards

Stefan

---------------------------------------------------------------------------


Full Bug description available at: http://bugs.php.net/?id=8311


-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to