If I prefix it with the file:// protocol I get these errors:
mod_xslt: I/O
mod_xslt: warning :
mod_xslt: failed to load external entity "proxy:///var/www/foo.xslt"
mod_xslt: couldn't load: file:///var/www/foo.xslt
(file:///var/www/foo.xslt), errno: 2
mod_xslt: fatal - couldn't load stylesheet for: proxy:http://localhost:387/
The pi for this page is:
<?xml-stylesheet type="text/xsl" href="file:///var/www/foo.xslt"?>
My apache config does have mod_proxy enabled, but is only used in
conjunction with a mod_rewrite match and should not be invoked for
this requested item.
I tried to compile the mod_xslt with --enable-debug but I don't see
any of the debug lines. Specifically I don't see the output from the
output from the debug statements in mxslt_doc_load, or
mxslt_doc_load_stylesheet (lib/modxslt-doc.c). Any thoughts? (Yes, I
have my LogLevel to debug in the conf file)
/colin
On 1/27/07, Denis F. Latypoff <latypoff@xxxxxxxxx> wrote:
Hello colin,
Saturday, January 27, 2007, 3:33:07 AM, you wrote:
> I am using the latest dev. snapshot for mod_xslt. I have an xml pi
> decl the location to my xslt inside the doc. However, when I request the
file I see errors like this:
> The href in the pi is explicitly set to /var/www/foo.xslt yet why
> is it trying to prepend the proxy:// protocol? I thought it would
> try direct file access first? If I change it to
> http://localhost/foo.xslt things work as expected.
perhaps using 'file:///var/www/foo.xslt' will help you.
> What is going on here? Where is this proxy uplift being applied?
Can you give your mod_xslt setup in the httpd.conf, full pi decl, etc?
> thanks for your help,
> /colin
> __________ NOD32 2010 (20070126) Information __________
> This message was checked by NOD32 antivirus system.
> part000.txt - is OK
