Hi Daan,

This is now fixed in the trunk and will be part of the 1.2.14 release. To use the fix, make sure you use the extractors that start with Hippo*, ie HippoSimpleXMLExtractor instead of SimpleXMLExtractor. The fix also prevents downloading of external public dtd's, so there could be some performance improvement.

Regards,
Bart

[EMAIL PROTECTED] wrote:
Hi Bart,

We're using a database for storage.
An example doctype declaration would be :

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE example SYSTEM "/opt/xpp/dtd/example/example.dtd">

Regards,
Daan

[EMAIL PROTECTED] wrote:
Hi all,
Hi Daan,

We recently ran into a problem with Hippo repository where a PUT request
for an xml file with a dtd reference resulted in a HTTP 406 (not
acceptable) statuscode. Apparently the repository tries to resolve(and
or
validate against) the dtd that was being referenced. On failing to
resolve
the dtd it choked and returned this statuscode.

Is there a way(preferably by configuration) to tell hippo not to try and
resolve and or validate against dtd's that might be referenced from xml
files that are being fed into the repository?
Can you provide an example file with which this is reproducable? Did you
use a file store or a database store?

Regards,
Bart


--

Hippo
Oosteinde 11
1017WT Amsterdam
The Netherlands
Tel  +31 (0)20 5224466
-------------------------------------------------------------
[EMAIL PROTECTED] / http://www.hippo.nl
--------------------------------------------------------------
********************************************
Hippocms-dev: Hippo CMS development public mailinglist



********************************************
Hippocms-dev: Hippo CMS development public mailinglist


--

Hippo
Oosteinde 11
1017WT Amsterdam
The Netherlands
Tel  +31 (0)20 5224466
-------------------------------------------------------------
[EMAIL PROTECTED] / http://www.hippo.nl
--------------------------------------------------------------
********************************************
Hippocms-dev: Hippo CMS development public mailinglist

Reply via email to