I recently upgraded from AxKit 1.4_82 to 1.5.2 in my Development and QA
environments. Unfortunately, I'm running into quite a few problems that
I could really use your help with.
1) the content of element names/attributes is escaped, while it wasn't
previously. for example, what was once:
<a href="javascript:void do_stuff(param1,param2)">
is now:
<a href="javascript:void%20do_stuff(param1%2Cparam2)">
Some browser versions don't like the new behavior, any idea how to fix
it?
2) XSP pages are not functioning.
When attempting to Post data from a form to an XSP page, which used to
function well, now returns a "Method Not Allowed" error from the web
server.
Simply going to an XSP page without submitting POST data returns an XML
document that has not been processed. In the Log file I see the
following when requesting the page:
[Wed Jun 12 11:27:00 2002] [warn] [client 208.229.127.4] [AxKit]
'/var/www/docroot/xsp/index.xsp' not recognised as XML
[Wed Jun 12 11:27:00 2002] [warn] [client 208.229.127.4] [AxKit]
provider declined
We have the following directives for handling XSP's:
<Files *.xsp>
SetHandler perl-script
PerlHandler AxKit
AxAddStyleMap text/xsl Apache::AxKit::Language::LibXSLT
AxAddStyleMap application/x-xpathscript
Apache::AxKit::Language::XPathScript
AxGzipOutput Off
</Files>
Any ideas on what would be causing any of these issues would be greatly
appreciated.
Thanks-
-R
Ryan Erwin
Oakley, Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
