Martha, my co-worker/supervisor, and I have been banging our heads against the wall for over two weeks about a bug in the system. Essentially, we've got a homegrown Python-based web server that serves content via localhost. Well, all of our Win32 installations were crashing if the user were to enter a quick Pythonserver-Form Button-Pythonserver cycle. Somehow, it'd choke on requests, and end up crashing in a way that it'd only work on non-form-button requests.
Martha finally found the problem today--because Win98 Internet Explorer somehow chokes on the way we're delivering the Content-type (it actually flashes to a page with just the Content-type displayed, and then forwards to the actual returned page). Windows 2000 and XP both handle it fine--it's just Windows 98. But since the original code was written for 98, we didn't foresee that the original bug "fix" would affect the new versions. Sigh.
Anyways, along the way, we discover:
- When a C-invoked Perl process (via the Win32
CreateProcess()) makes the system call for `ver`, Windows 98 returns nothing. Win2k and XP, however, act normally.
- Internet Explorer is perfectly fine handling html content without an actual Content-type field.
- Internet Explorer is largely fine handling html content without valid HTTP headers (said headers can be either " "--yes, that's a blank space--or a Content-type with just a single newline--no, there are no other headers to add a second newline).
But, thankfully, it's all fixed now. I wonder how many dumb Microsoft workarounds have seriously screwed people over when using later versions of their products?
Raise your hand if you want Kill Bill
to be Quentin Tarantino's documentary about Microsoft...
And in a geeking out of another kind, I'm off to Dragoncon at noonish--I'll be the tall Chinese guy with the bright orange Blue Man Group shirt, hanging around the Buffy track. Say hey if you care to.Current Mood: