ID: 24666
Updated by: [email][/email]
Reported By: dhunter at uta dot edu
-Status: Feedback
+Status: No Feedback
Bug Type: Apache related
Operating System: Solaris 8
PHP Version: 4.3.2
New Comment:

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.

Previous Comments:

[2003-08-13 21:41:04] [email][/email]

Please try using this CVS snapshot:


For Windows:



[2003-08-05 15:54:51] dhunter at uta dot edu

I did this prior to submitting the bug. See Description.
- Thanks


[2003-08-05 15:10:25] [email][/email]

Take at a look your apache's primary error log file, see if there are
any messages from php or reports of crashed apache children.


[2003-07-22 22:26:14] dhunter at uta dot edu

I've had php logging on the entire time. That's the reason I haven't
been able to track this down. We have been using php extensively for a
long time and I've never experienced this before. When a page prints
blank the access log entry is:

[url][/url] - - [22/Jul/2003:21:59:00 -0500] "GET
/uta/current HTTP/1.1" 200 5 "" "Mozilla/4.0
(compatible; MSIE 5.0; AOL 8.0; Windows 98; DigExt)"

The same page should report 22430 bytes like the following:

[url][/url] - - [22/Jul/2003:22:09:57 -0500] "GET
/uta/current HTTP/1.1" 200 22430 "-" "Mozilla/5.0 (X11; U; Linux i686;
en-US; rv:1.4b) Gecko/20030516 Mozilla Firebird/0.6 StumbleUpon/1.73"

What could have changed between 4.3.1 and 4.3.2 that could cause this.


[2003-07-21 18:03:13] [email][/email]

Try to enable logging of php errors and see if the php error contains
any errors that could explain the cause for the blank pages.


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

Edit this bug report at [url][/url]