| I needed something to kill some time anyhow ;)
I tried pasting in the server response headers from a 'normal' web hit, thinking it was the content type or encoding or something that was freaking IE out. No dice.
Now, I'm thinking we need to wait for IE to send the request before answering it. Basically, just waiting for an empty line on STDIN and then spitting out the headers and file.
Am I correct in assuming that /tmp/reportsock is a FIFO being written to by a monitoring process?
Anyhow, I'll hack together a perl script to emulate a 'correct' HTTP response. Just give me a moment to clear off something else first ;)
pyro |