Re: iframe cgi error
| From: | Richard Lynch | Date: | Mon, 12 May 2003 08:47:53 +0000 |
| Subject: | Re: iframe cgi error | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-147274@lists.php.net to get a copy of this message | ||
Bruce Levick wrote:
I am experiencing a strange error I have not yet seen on my local server. (IIS, winxp pro, latest php, mySql). I have a page which has an IFRAME. The page within the iframe calls a simple(very simple) select query on a DB. When I test the page within the iframe on my local server i receive this error: "The specified CGI application misbehaved by not returning a complete set of HTTP headers. The headers it did return are:" and the rest is blank. But when I test this page seperately (outside the iframe). It works the way it should (displays the selection from the DB). Any clues as to why this might be happening??No... But some ideas on how to attack it. 1. Get rid of IFRAMES which are too browser-dependent and flaky in the first place :-) 2. Check your web-server error logs. Errr... I'm assuming IIS actually *HAS* some kind of logging going on. Anyway, see if there is any more info being logged about the request and what happened. 3. Try putting <?php phpinfo();?> in the IFRAME code (instead of the db stuff) and compare the output with and without the IFRAME. Perhaps something "different" will appear... Most likely, the CGI error is happening long before PHP actually gets invoked, mind you, but it's worth a shot, since it will take only a minute. 4. Switch from using PHP as a CGI to using the ISAPI DLL instead. Read the PHP install instructions. TEST ALL PHP MODULE DLLs THOROUGHLY UNDER HEAVY LOAD!!! Last time I checked, *some* of the PHP DLL Modules were still not thread-safe, and would fail "intermittently" under heavy load. YMMV. Maybe they've all been fixed. How could you tell with Windows crashing all the time anyway? :-) 5. Make your browser window very very small. See if you can spot the PHP MS-DOS window firing up that executes the PHP CGI, and, with any luck at all, manage to pause/crash/stop Windows in such a way that you can "catch" the output of that window. I managed this only once, and it requires a lot of time playing Tetris to get fast enough on the keyboard. YMMV. I can't guarantee XP actually creates/displays such a window. Never used XP. Never will. No more Windows. Hmmm. Maybe you could alter your IIS settings to convince it to fire up PHP and pipe/tee the output somewhere... Assuming XP *has* pipe/tee or you can install them somewhere. 6. Upgrade to a Un*x server. :-)