Re: [xslt] XSLT and Safari
- From: Dave Hyatt <hyatt apple com>
- To: The Gnome XSLT library mailing-list <xslt gnome org>, veillard redhat com
- Cc:
- Subject: Re: [xslt] XSLT and Safari
- Date: Wed, 11 Aug 2004 12:01:11 -0700
At the moment I use RegisterInputCallbacks to just stop libxml from
doing all I/O. I implemented a match function that always returns 1
and an open function that always returns NULL. Is that sufficient to
stop all of libxslt's I/O? So what are all the possible ways libxslt
can read a document? I need to know how to catch these so I can parse
the docs myself, and you can assume I'll need API callbacks for all of
these...
dave
(hyatt apple com)
On Aug 11, 2004, at 2:23 AM, Daniel Veillard wrote:
On Tue, Aug 10, 2004 at 03:57:21PM -0700, David Hyatt wrote:
I can figure out all the imports/includes, use our own security
routines and recursion defenses when loading, and ultimately end up
with a bunch of xmlDocPtrs. What I'd then like to do is be able to
As a reminder, with exslt:document set of extensions, a stylesheet
can output documents, you absolutely want to check the security API
http://xmlsoft.org/XSLT/html/libxslt-security.html
anyway to block those writes.
Also note the document() XSLT function does read at run-time,
you will need to catch those too I assume, the function is
xsltDocumentFunctionLoadDocument()
which call
xsltLoadDocument()
itself calling
xsltParseDocument() too
xsltParseDocument() seems central to the callback API to be designed,
it may come at parsing time or at runtime, but always need a
dictionnary.
Daniel
--
Daniel Veillard | Red Hat Desktop team http://redhat.com/
veillard redhat com | libxml GNOME XML XSLT toolkit
http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
_______________________________________________
xslt mailing list, project page http://xmlsoft.org/XSLT/
xslt gnome org
http://mail.gnome.org/mailman/listinfo/xslt
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]