I've found what may be a small bug in processing XSP files. I noticed this due to my normal file naming conventions - I often use the filename "core.html", etc.
I didn't notice any mention of this in the documentation, so I'm posting it here. When I attempt to process an XSP file named core.xsp, AxKit delivers it as plain text. I've reduced the scenario to the following test case based on the sample XSP file given in the guide on the axkit.org site. Given the following file: <xsp:page [xmlns and language attribute declarations here]> <page> The time is: <xsp:expr>scalar localtime</xsp:expr> </page> </xsp:page> It will display as plain text if it is saved as "core.xsp" but will transform properly if given any other file name. No errors are reported to the log regardless of the AxDebugLevel value set in httpd.conf. My system is an Apache 1.3.26 with mod_perl 1.26, perl 5.6.1 and AxKit 1.6 running on FreeBSD 4.4-RELEASE. Sincerely, S. G. Kearn --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
