|Jon Leech||Feb 23, 2009 12:24 pm|
|Grosso, Paul||Feb 23, 2009 12:31 pm|
|Jon Leech||Feb 23, 2009 12:50 pm|
|Adam Constabaris||Feb 23, 2009 1:40 pm|
|William R. (Bill) Greene||Feb 24, 2009 4:44 pm|
|Keith Fahlgren||Feb 24, 2009 5:06 pm|
|William R. (Bill) Greene||Feb 24, 2009 5:48 pm|
|Bob Stayton||Feb 24, 2009 5:55 pm|
|DavePawson||Feb 26, 2009 2:41 am|
|Jon Leech||Mar 8, 2009 3:28 am|
|Bob Stayton||Mar 8, 2009 10:47 am|
|Michael(tm) Smith||Mar 10, 2009 1:37 am|
|Subject:||Re: [docbook] w3.org won't serve DTD imbedded in Docbook generated output - but only to IE|
|From:||Michael(tm) Smith (smi...@sideshowbarker.net)|
|Date:||Mar 10, 2009 1:37:37 am|
For more info on this problem and how the W3C systems deal with it, see:
"Grosso, Paul" <pgro...@ptc.com>, 2009-02-23 15:32 -0500:
This has nothing to do with docbook.
Send email to webm...@w3.org for something like this.
But your application probably shouldn't be trying to retrieve a resource at that URL. If everyone always hit the W3C server every time they did anything with XHTML it would be a disaster, and most likely what you are seeing is the result of some code put in by the W3C webmaster to prevent just this.
-----Original Message----- From: Jon Leech [mailto:jo...@alumni.caltech.edu] Sent: Monday, 2009 February 23 14:25 To: docb...@lists.oasis-open.org Subject: [docbook] w3.org won't serve DTD imbedded in Docbook generated output - but only to IE
We're having a weird problem with some content generated by Docbook, such as
At some time relatively recently, this has started failing with IE, although it still works fine with Firefox. Our server admin has chased this down as far as finding out that when
is fetched with an IE 7 User-Agent, it's rejected by www.w3.org with the following resulting from the HTTP dialog:
HTTP/1.1 503 Go away Date: Mon, 23 Feb 2009 13:32:48 GMT Server: Apache/2 Content-Location: msie7.asis Vary: negotiate,User-Agent TCN: choice Retry-After: 86400 Cache-Control: max-age=21600 Expires: Mon, 23 Feb 2009 19:32:48 GMT P3P: policyref="http://www.w3.org/2001/05/P3P/p3p.xml" Content-Length: 2 Connection: close Content-Type: text/plain
Looking at the P3P document referenced from this doesn't shown any obvious reason for the error. I tried to figure out an appropriate W3C mailing list to inquire on but there are dozens of them and nothing springs out as being obviously relevant. Has anyone else run into this? Any idea what's happening and how we might address it?
-- Michael(tm) Smith http://people.w3.org/mike/