Don is right. We shouldn't fix this on the server because IE is
braindead in handling this error code. One supposedly new
feature of AOLserver 3.2: it detects IE and automagically
replaces 500 error codes with more IE-friendly data. Can anyone
confirm that this works? Haven't had time to try aolserver 3.2 just
yet.
