Sorry, I meant to send this to the group...

--- Begin Message ---

I had this problem too. I was in the middle of some changes, and I
thought, "What the heck...It's just a minor upgrade...". Not long
after I upgraded (and I think right after I made a change to
httpd.conf) all my xsp pages stopped working. I was scratching my head
for about 3 hours, figuring that I had mispelled something somewhere.

I played with different ways of configuring Apache, and ended up going
from:

<Files "*.xsp">
                 SetHandler perl-script
                 PerlHandler AxKit
                 AxAddStyleMap text/xsl Apache::AxKit::Language::LibXSLT
                 AxAddStyleMap application/x-xsp Apache::AxKit::Language::XSP
                 AxAddXSPTaglib AxKit::XSP::ESQL
                 AxDebugLevel 5
                 AxStackTrace On
                 AxLogDeclines On
</Files>

to this:

PerlModule AxKit

AddHandler axkit .xsp
AxDebugLevel 5
AxStackTrace On
AxLogDeclines On

AxAddStyleMap text/xsl Apache::AxKit::Language::LibXSLT
AxAddStyleMap application/x-xsp Apache::AxKit::Language::XSP

AxAddXSPTaglib AxKit::XSP::ESQL
AxAddXSPTaglib AxKit::XSP::PerForm

AxAddPlugin Apache::AxKit::Plugin::Passthru

(i.e., not inside a <Files block>)

It worked, and I was tired, so I let it lie. It sure is nice to no I'm
not insane now though. Now I think I will go back and resume using
<Files>, after adding a type for my xsp documents. Thanks for
mentioning this.

--chris

--- End Message ---

-- 
--chris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to