Hi!
Can someone tell me how to avoid the delivery of raw xml/xsp files? This
happens when I try to transform it with a "not well-formatted" xsl
stylesheet. I already discovered the configuration paramter
AxErrorStylesheet. But this only applies to errors which happen during
xml/xsp parsing. However, if I have a xsp file which generates me proper
xml output and now try to transform it with
Apache::AxKit::Language::Sablot using a broken xsl stylesheet - then
AxKit delivers the rax xsp file to the client. This may be particularly
bad, when using e.g. the ESQL taglib and hence stored some database
password in your xsp file.
Any hints/suggestions how to get around this problem?
Thanks,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
- Re: avoid delivery of raw xml/xsp files Martin Bahlinger
- Re: avoid delivery of raw xml/xsp files Matt Sergeant
- Re: avoid delivery of raw xml/xsp files Tom Howe
- Re: avoid delivery of raw xml/xsp files Martin Bahlinger
- Re: avoid delivery of raw xml/xsp files Tod Harter
- Re: avoid delivery of raw xml/xsp files Martin Bahlinger
- Re: avoid delivery of raw xml/xsp f... Sebastian Rahtz
- Re: avoid delivery of raw xml/x... Martin Bahlinger
- Re: avoid delivery of raw xml/x... Matt Sergeant
