So now I turn to my friends at my favorite woodworking forum for a rather strange and technical problem... Not even Google seems to know what's going on here. 
I'm trying to set up one of my sites on a Linux host using Drupal instead of ASP.NET. And everything seemed to be going fine until I tried to open the site in IE.
In IE (but not firefox) I started getting blank pages randomly. Hit refresh and the content is back. Hit refresh a few more times, and it's there again. Hit refresh again, and it's blank. Same page -- just hitting refresh. I view the source and it cuts off at the same place every time it breaks -- right in the middle of a tag, actually. Other pages act similarly, but cut off in different places -- again randomly, but enough to impact users (maybe 1/20 times, sometimes a few times in a row.)
The page is not caching. It happens from three different computers on 3 different IP addresses on 3 different ISPs. It has happened on the first time I visited any page on the site from a computer/IP/ISP that has never visited the site.
So out comes Wireshark. I'm no pro at wireshark, but I fumbled my way through to reproduce the problem -- one failure and one success in the same capture. From what I can tell, the ENTIRE page is returned each time -- just as it should be. So how can IE be arbitrarily and randomly cutting it off?
Could there be something in the TCP conversation that gives IE the idea that it's done when it's not? (e.g. server tells IE, "you're going to get 10 packets" but actually sends 20.)
Any ideas out there? Please let me know if you have any ideas or you think you can help... This is really driving me up a wall and I'd much rather me in the shop than reading through packets! (yuck!
)
Thanks!

I'm trying to set up one of my sites on a Linux host using Drupal instead of ASP.NET. And everything seemed to be going fine until I tried to open the site in IE.
In IE (but not firefox) I started getting blank pages randomly. Hit refresh and the content is back. Hit refresh a few more times, and it's there again. Hit refresh again, and it's blank. Same page -- just hitting refresh. I view the source and it cuts off at the same place every time it breaks -- right in the middle of a tag, actually. Other pages act similarly, but cut off in different places -- again randomly, but enough to impact users (maybe 1/20 times, sometimes a few times in a row.)
The page is not caching. It happens from three different computers on 3 different IP addresses on 3 different ISPs. It has happened on the first time I visited any page on the site from a computer/IP/ISP that has never visited the site.
So out comes Wireshark. I'm no pro at wireshark, but I fumbled my way through to reproduce the problem -- one failure and one success in the same capture. From what I can tell, the ENTIRE page is returned each time -- just as it should be. So how can IE be arbitrarily and randomly cutting it off?
Could there be something in the TCP conversation that gives IE the idea that it's done when it's not? (e.g. server tells IE, "you're going to get 10 packets" but actually sends 20.)
Any ideas out there? Please let me know if you have any ideas or you think you can help... This is really driving me up a wall and I'd much rather me in the shop than reading through packets! (yuck!
) Thanks!

...at least not in the past 10 minutes or so. I'm keeping my fingers crossed!
Comment