Welcome to WebmasterWorld Guest from 220.127.116.11
Forum Moderators: phranque
The OS is WIN98 2nd Ed.
McAfee Firewall - disabled for our testing.
I have NO IDEA what to tell this fellow. Checking my logs there are no errors associated with the IP address. The logs appear normal.
The page in question is a PHP page, with a REWRITE rule in place to display the html page name in the browser address bar... same as hundreds of other pages on the site.
Any suggestions? I'm going to pop over to MS and see what I can find also.
When I still had 98SE on my main box, I did have issues sometimes with online catalogs. I always thought it was a RAM thing, since I had only 98mb.
I do still have 98SE on my antique laptop, with only 64mb RAM, and once I'm online, I almost cannot simply load catalog pages. I never even ATTEMPT to actually ORDER something.... As well, after I've BEEN online for a while (I feel like that's in the neighborhood of over 30 minutes though I haven't really "timed" it), I can't even get new pages to load.
I'll call him tomorrow and ask about RAM. That actually might make sense. I continue to make my pages bigger and bigger with PHP - trying to cram as much product as possible onto a single page. The customer has not had this problem in the past on my site, either, when I hard coded everything onto a regular html document. Those pages were generally smaller.
I found something on MS about web pages with really long names causing a buffer overrun (W95 and W98), but this problem reports a hang, not a re-boot. Just curious, POST'ing all my data should not be causing any long names, since everything is sent in the header. What about really long header info tho? I think the only possible scenario with this particular item would be the cart sending back a really long name - ie., royally screwing up the return page. I don't believe that for a minute.
I don't THINK I ever had problems with long-header strings though - wouldn't you get some sort of off-the-wall error message with that? Or if the machine is going into the reboot cycle with it, you'd at least (I think) see the BSOD....
What I can now tell him is that he MIGHT:
<add>I checked my page again, and it was NOT valid html. <smack>I corrected that, and now also provide header information.</add>
But sometimes the impossible happens. I would only worry if I got multiple occurences of the same problem.