Network Packet size affecting how HTML is served?

[tlhawkins]

Hey,

This is a little out of my area of knowledge so I may not be making a lot of sense. Someone just tell me if I'm not.

I have an HTML page that displays differently on 1 server than another. The process is to output a small page with a "Wait" message, flush that to the browser and then finish creating the rest of the page and flush that to the browser when it's done. This creates a "Processing..." kind of page and I have it working on 3 different servers but, of course, the server I need it to work on it doesn't.

Instead this server waits until the whole process is done before sending anything to the browser. It's the exact same code that is working on 3 other servers. So I started to think about what could be holding up sending data to the browser and I wondered if the network packet size could be causing this "cached" affect where data isn't served until it's completely finished?

Please let me know of anything you think could be causing this.

Thanks

Travis Hawkins

http://www.bestcodingpractices.com

 

[markdmac]

Check for different browser versions. Get everything on the same (and latest) patches.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.

 

[tlhawkins]

I figured out the problem, and it wasn't related to packet size at all. It turns out someone turned on some kind of 3rd party compression ISAPI module for IIS. It could send a partially finished compressed file, but it couldn't uncompress the file at the other end until it was all available, so it looked like it was waiting to send it.

Thanks for all who looked into this for me.

Travis Hawkins

http://www.bestcodingpractices.com