On Mar 3, 2011, at 01:37, Nate wrote:
> Your post was great and led me to find this particular problem causing the issue, but I still haven't solved the problem.
>
> These apache handlers are causing the issue:
> <LocationMatch "(\.html)$">
> SetHandler perl-script
> PerlHandler HTML::Mason::ApacheHandler
> </LocationMatch>
>
> #Hide private components from users.
> <LocationMatch "(dhandler|autohandler|\.mas|\.m(html|txt|pl))$">
> SetHandler perl-script
> PerlInitHandler Apache::Constants::NOT_FOUND
> </LocationMatch>
>
> The above are Mason handlers which need to be there, but not for the directory where we try and check code in.
>
> The location handlers are causing me the headache. This is tougher to solve than I originally thought. Is there any way to disable these handlers for a subdirectory? I've tried a ton of things to do it already, but pretty much every combination has failed.
>
> The URI location would be under /myfolder
> The physical location on the server would be /usr/local/myfolder
>
> Adding this line to the httpd.conf file changed the behavior:
> <Location /myfolder>
> SetHandler default-handler
> </Location>
>
> Here's the error message now:
> Server sent unexpected return value (500 Internal Server Error) in response to CHECKOUT request for '/myfolder YADDA YADDA'
>
> Any clues on how to disable the apache directives for /myfolder?
Before you were getting an error on a PROPFIND, now on a CHECKOUT. These are WebDAV methods that Subversion uses but that presumably your web site doesn't... would it work to limit the Mason directives to just GET and POST requests?
<Limit GET POST>
<LocationMatch "(\.html)$">
SetHandler perl-script
PerlHandler HTML::Mason::ApacheHandler
</LocationMatch>
#Hide private components from users.
<LocationMatch "(dhandler|autohandler|\.mas|\.m(html|txt|pl))$">
SetHandler perl-script
PerlInitHandler Apache::Constants::NOT_FOUND
</LocationMatch>
</Limit>
Received on 2011-03-03 16:19:56 CET