--- Justin French <[EMAIL PROTECTED]> wrote: > In NN7 Mac, the error is "the page contained no data". > In IE5.x Mac, the error is along the lines of "host > not found" or "could not access URL ...".
This is a bit off-topic, but I would suggest ignoring any error messages from IE. It will generally "hide" the real error and show you some generic page instead. This can be very misleading. Go with Netscape's assessment of the problem. > I guess what I'm hoping for is some wild stabs in the > dark as to what the problem might be, and where I > might start looking. There are a few different ways you can get a "document contained no data" message: 1. You have an endless loop somewhere in your code, so that under certain circumstances, the script never completes. 2. You have an endless loop in the form of protocol-level redirects (using header()), so that the Web client continues to make HTTP requests without ever receiving a 200 response. 3. The network connection is terminated. This can occur when the server crashes, among other things. I can think of no other ways to receive this error (please, someone chime in if I have left one out). So, you can try to rule out possibilities one by one. Endless loops in your code might be difficult to identify if the logical path through your code required to generate it is rare. Sometimes looking through your code with this in mind is the best way to find the problem. Endless amounts of protocol-level redirects can be detected pretty easily. If you can reproduce it in any way, tcpdump or some other debugging tool can reveal the HTTP transactions. Short of this, many requests within a very small window of time from the same IP is a good indicator as well. If the Web server crashes under certain circumstances to cause this error, this can be the most difficult to track down. Your best bet is to be able to at least reproduce the steps necessary to crash the server. If you believe it might be only demonstrable under load, you will want to test the application under heavy load to see if you can reproduce the error. > - (occasionally) makes use of header() redirects I would recommend looking at these first. Make sure there is no way for the client to enter into an endless loop of redirects. Anyway, I hope that helps. Sometimes just knowing some common cases that result in the same error can help you identify the problem. Good luck. Chris -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
