On a few sites I maintain we have several man pages setup using XML and XSL. This week started getting complaints from Windows IE users saying they can’t see the man pages any more. The error message is:
The XML page cannot be displayed
Cannot view XML input using style sheet.
Please correct the error and then click
the Refresh button, or try again later.
The server did not understand the request,
or the request was invalid. Error processing resource
The header of my page has this in it:
When I try to access either http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd or http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd in any browser except Windows IE, the page loads or downloads as expected. In Windows IE the only thing that is served up is “No”.
I am curious of others are seeing this. Is it a Microsoft problem? Is it a W3.org problem? As it is Windows IE users appear to be out of luck. Perhaps w3.org simply has had enough of Windows IE and wants them to go away?
I would love to hear other people results on trying to load these URL’s and their comments.
curl http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd -D ./dump.txt -A “Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322)”
HTTP/1.1 503 Go away
Date: Mon, 23 Feb 2009 13:48:30 GMT
Expires: Mon, 23 Feb 2009 19:48:30 GMT
curl http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd -D ./dump.txt -A “Mozilla/4.0 (compatible; Windows NT 5.1; .NET CLR 1.1.4322)”
The entire DTD file successfully lists
HTTP/1.1 200 OK
Date: Mon, 23 Feb 2009 13:50:22 GMT
Last-Modified: Thu, 01 Aug 2002 18:37:56 GMT
Expires: Sun, 24 May 2009 13:50:22 GMT
Content-Type: application/xml-dtd; charset=utf-8
Further research shows that the offending User-Agent string would appear to be MSIE. Removal of MSIE or any change to MSIE results in a successful return of the DTD.
I tried contacting w3.org last week when I first posted this, but obviously I have the wrong contact info as no one has responded yet.
This is a known issue related to W3C’s excessive traffic . We are
working with Microsoft, and a fix is expected in coming months.
It would appear that Windows IE is attempting to load the DTD on each page load, which is improper behaviour. Perhaps the only solution at this point is to host a copy of the DTD on our own server so that Windows users can still read the XML pages.
Thoughts and suggestions are always welcome.
With one of my clients I need to monitor email bounces from our mailing lists. Normally this goes relatively smoothly, as either the email goes through, or it bounces back with a 550 Recipient not found message. Sometimes the messages I get back are less familiar to me. Here is the appendix from RFC1893. Hopefully this will be a useful guide:
X.1.0 Other address status
X.1.1 Bad destination mailbox address
X.1.2 Bad destination system address
X.1.3 Bad destination mailbox address syntax
X.1.4 Destination mailbox address ambiguous
X.1.5 Destination mailbox address valid
X.1.6 Mailbox has moved
X.1.7 Bad sender’s mailbox address syntax
X.1.8 Bad sender’s system address
X.2.0 Other or undefined mailbox status
X.2.1 Mailbox disabled, not accepting messages
X.2.2 Mailbox full
X.2.3 Message length exceeds administrative limit.
X.2.4 Mailing list expansion problem
X.3.0 Other or undefined mail system status
X.3.1 Mail system full
X.3.2 System not accepting network messages
X.3.3 System not capable of selected features
X.3.4 Message too big for system
X.4.0 Other or undefined network or routing status
X.4.1 No answer from host
X.4.2 Bad connection
X.4.3 Routing server failure
X.4.4 Unable to route
X.4.5 Network congestion
X.4.6 Routing loop detected
X.4.7 Delivery time expired
X.5.0 Other or undefined protocol status
X.5.1 Invalid command
X.5.2 Syntax error
X.5.3 Too many recipients
X.5.4 Invalid command arguments
X.5.5 Wrong protocol version
X.6.0 Other or undefined media error
X.6.1 Media not supported
X.6.2 Conversion required and prohibited
X.6.3 Conversion required but not supported
X.6.4 Conversion with loss performed
X.6.5 Conversion failed
X.7.0 Other or undefined security status
X.7.1 Delivery not authorized, message refused
X.7.2 Mailing list expansion prohibited
X.7.3 Security conversion required but not possible
X.7.4 Security features not supported
X.7.5 Cryptographic failure
X.7.6 Cryptographic algorithm not supported
X.7.7 Message integrity failure