W3 blocking DTD access from VisualWorks

 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd' asURI resource

produces HTTP 403 Forbidden...at least on all of my build machines. I'm
guessing this is a response to:

http://www.w3.org/blog/systeam/2008/02/08/w3c_s_excessive_dtd_traffic

Other's are struggling with this too (a quick search shows microsoft's
parsers were hit by this).  Does Cincom's XML parser have a way to work
around this?  I'm guessing that w3 has just black-listed the user agent
reported by VW since downloading the DTD url in chrome works fine...this
is just a guess though.

Last year I hacked together a DTD caching mechanism for SeasideTesting
but it was a horrible hack.  In that case I not only wanted to cache the
contents of the DTD but also the parsed version.  I'm modifying it so
that it will never request the XHTML DTD used by Seaside but I'm
guessing anyone using VW to parse XHTML is going to be frustrated by
this problem.

David

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

You bet! Even before they started blocking people, it was far too slow to actually fetch the DTD from their servers so typically you'd take a copy locally. The way you divert traffic away from the web and answer it locally is with XML.PluggableEntityResolver. The class comments describe how it works. You can respond with nothing for an entity or have it do the standard behavior or return your own contents for the entity in the block.

Michael

On Oct 30, 2010, at 9:11 AM, C. David Shaffer wrote:


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

David,

For years there has been a parcel in the contributions folder called
GHSpeedupXMLParser. It's main purpose is to cache DTDs. Did you give it a
try?

Georg

Georg Heeg eK, Dortmund und Köthen, HR Dortmund A 12812
Tel. +49-3496-214328, Fax +49-3496-214712
-----Ursprüngliche Nachricht-----
Von: [hidden email] [mailto:[hidden email]] Im Auftrag
von Michael Lucas-Smith
Gesendet: Samstag, 30. Oktober 2010 21:06
An: C. David Shaffer
Cc: vwnc
Betreff: Re: [vwnc] W3 blocking DTD access from VisualWorks

You bet! Even before they started blocking people, it was far too slow to
actually fetch the DTD from their servers so typically you'd take a copy
locally. The way you divert traffic away from the web and answer it locally
is with XML.PluggableEntityResolver. The class comments describe how it
works. You can respond with nothing for an entity or have it do the standard
behavior or return your own contents for the entity in the block.

Michael

On Oct 30, 2010, at 9:11 AM, C. David Shaffer wrote:


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc



_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

 On 10/30/10 16:43, Georg Heeg wrote:
> David,
>
> For years there has been a parcel in the contributions folder called
> GHSpeedupXMLParser. It's main purpose is to cache DTDs. Did you give it a
> try?
>

Cool, thanks for the pointers.  I was able to get
XML.PluggableEntityResolver working (and borrowed some code from the VW
Seaside/SUnit support to get character entities to be recognized).  I
can't find GHSpeedupXMLParser anywhere in vw7.7 or 7.7.1 for that
matter.  I also looked on the public store repository.  Is it possible
that the name is off or that it is part of other packages?

FWIW, SeasideTesting has cached DTD's for years...but it always requests
the DTD once after an image startup, parses it and caches the parsed
result.  This has been /very/ efficient.  The problem not is that W3C is
rejecting that first request for the DTD.  Seems like they've
black-listed the VW client.

David



_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

David,

GHSpeedupXMLParser is located in $(VISUALWORKS)\contributed\Heeg\. If you
don't have that directory, you have to install it from your distribution.

Georg

Georg Heeg eK, Dortmund und Köthen, HR Dortmund A 12812
Tel. +49-3496-214328, Fax +49-3496-214712

-----Ursprüngliche Nachricht-----
Von: [hidden email] [mailto:[hidden email]] Im Auftrag
von C. David Shaffer
Gesendet: Sonntag, 31. Oktober 2010 02:59
An: 'vwnc'
Betreff: Re: [vwnc] W3 blocking DTD access from VisualWorks

 On 10/30/10 16:43, Georg Heeg wrote:
> David,
>
> For years there has been a parcel in the contributions folder called
> GHSpeedupXMLParser. It's main purpose is to cache DTDs. Did you give
> it a try?
>

Cool, thanks for the pointers.  I was able to get
XML.PluggableEntityResolver working (and borrowed some code from the VW
Seaside/SUnit support to get character entities to be recognized).  I can't
find GHSpeedupXMLParser anywhere in vw7.7 or 7.7.1 for that matter.  I also
looked on the public store repository.  Is it possible that the name is off
or that it is part of other packages?

FWIW, SeasideTesting has cached DTD's for years...but it always requests the
DTD once after an image startup, parses it and caches the parsed result.
This has been /very/ efficient.  The problem not is that W3C is rejecting
that first request for the DTD.  Seems like they've black-listed the VW
client.

David



_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc



_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc