ID: 18371 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Apache2 related Operating System: ALL PHP Version: 4.3.0-dev New Comment:
Wow... incredible... now i'm getting the same error with SSL too. That's really boring! The people need a safe way to run php... but there isn't any up-to-date solution that really works (especially apache2/cgi). It's hard to believe that php will run at any ISP, when there are so great problems with it. Apache2 is much better in managing resources and has more speed... so it will be the next step in webhosting-environments, please fix it soon. Previous Comments: ------------------------------------------------------------------------ [2002-11-11 10:02:07] [EMAIL PROTECTED] Uhm... allways the same... look above :/ ------------------------------------------------------------------------ [2002-11-11 10:00:35] [EMAIL PROTECTED] There is something different... i thing the line numbers ;) --------- Warning: Unexpected character in input: '' (ASCII=16) state=1 in /pool/php4/bin/php-cgi on line 5409 Parse error: parse error, unexpected '*' in /pool/php4/bin/php-cgi on line 5409 --------- ------------------------------------------------------------------------ [2002-11-11 09:46:40] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php4-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-latest.zip ------------------------------------------------------------------------ [2002-11-11 08:08:51] [EMAIL PROTECTED] *oops* read above ------------------------------------------------------------------------ [2002-11-11 08:07:15] [EMAIL PROTECTED] Nope, isn't fixed... Output: --------- Warning: Unexpected character in input: '' (ASCII=16) state=1 in /pool/php4/bin/php-cgi on line 5398 Parse error: parse error, unexpected '*' in /pool/php4/bin/php-cgi on line 5398 --------- Same as before :( And i tried it with: php4-STABLE-200211101739 ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/18371 -- Edit this bug report at http://bugs.php.net/?id=18371&edit=1
