So this week we launch a web site that uses SSL. Wierd problems ensue for people who are using IE 6.0 on Windows XP - a scarily common configuration.
An analysis of the symptoms seems to suggest that the browser is sending a POST with no content. Note, this is quite different from the form being submitted with no fields completed. In our case not even the field names were received although it was a post request and it did have a non-zero Content-length header.
Turns out it's a bug - introduced by a recent security patch.
It goes like this:
Do these people not do regression testing?
The thing that pisses me off the most, is that the browser is broken, but we have to implement a workaround on the server (disable KeepAlive) so it looks to all the world like we had a bug and we fixed it.
Another solution would have been to give them a link to the knowledge base article about the bug with a brief explanation and explain that it includes a link to the critical update that is intended to fix it. This is not the best solution because it points fingers. It does, however, clearly remove any blame from your company.
Thanks so much for putting this in your log and putting up the link. Now we can suggest they update their computer to see if that works.
On a personal site you can always encourage IE users to upgrade to a better browser. It's a bit cheeky, but you can implement Dead Edwards noIE css trick. I've patched mine to link to the Broswe Happy site, as I don't mind what people use, as long as it's not IE.