Opening index.php dialog box triggered

Here’s a weird thing. One of my pages started triggering this dialog:



The page loads fine at first, but has a form. When you click the submit button (which submits the form to the same page), then this thing pops up. Quite odd. It seems to think that it’s a zip file. In my .htaccess file I have the zlip compression stuff all off so that’s not it. I just can’t explain it...

Currently I’m in the process of trimming my form snippet down to nothing trying to identify where my code might be doing something odd. But so far no luck.

I’d sure appreciate some ideas!

I get that from time to time on this PowerBook, but the hard drive is slowly fading and when I get this (or see the icons for the files all wierd in Finder) it’s time to run Norton Disk Doctor and repair the file system. Then everything is fine for a couple more weeks.

Since that’s Windows, I would suggest checking your Registry.

This glitch isn’t browser or platform dependent. It happens on my machine, my coworkers machine, my Mac...

Speaking of the Mac, I did get a different error message from it:

The error was: "bad server response"
(NSURLErrorDomain: -1011)

So looks like I’ll be doing some Googling.

update
This seems to simply be Macs way of saying "I don’t know what to do with this." Not much in the way of useful diagnostic information.

I’ve narrowed down to a class function I wrote. Which is weird. Is there some sort of limit to the amount of memory a PHP script is allowed to use? The function returns a potentially large-ish recordset (as many as 5,000 rows, but typically about 800). When I run the function from an otherwise empty test bed snippet, it does fine, but from my "real" snippet which has other queries etc. in it, it gives me this problem when dealing with the larger recordsets. Is this a clue or a red herring...

What exactly is the "action" for your form?

Yes, there are limits both on memory and on time. Your phpinfo will tell you what it is. But that will generate an error.

Action is an empty string actually. It’s not timing out - it doesn’t take long. But I think it is hitting some server/PHP imposed limit of some variety. I was chatting with Opengeek and he suggested it might be an inefficiency in how I’m converting the recordset to a gigantuous array

But since I’m under a pretty well defined deadline (translation: rush), I’ve come up with a different way to approach the problem which will require a small additional user step, but will decrease the PHP/MySQL logic substantially.

Did you accidentally switch the content type of the document to attachment by any chance?

Negatory. The conent type is still the same. Oh well. Moving on. I think we should consider this issue dead unless it hits someone else or it can be replicated on a public server (my issue is on an intranet server).