Here's a patch to allow the Script directive to handle
arbitrary (e.g., site-specific or experimental) methods.
Current 2.0 behaviour is 'if it's not something hard-coded
into me, it's rubbish and gets tossed.'
I notice that this functionality already exists in trunk,
so this is essentially a feature^Woversight-correction backport.
As to why I came across this.. I think there's a bug in PUT
handling on 2.0. Trying to track it down..
--
#ken P-)}
Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/
Author, developer, opinionist http://Apache-Server.Com/
"Millennium hand and shrimp!"
Index: mod_actions.c
===================================================================
--- mod_actions.c (revision 507150)
+++ mod_actions.c (working copy)
@@ -103,12 +103,13 @@
int methnum;
methnum = ap_method_number_of(method);
- if (methnum == M_TRACE)
+ if (methnum == M_TRACE) {
return "TRACE not allowed for Script";
- else if (methnum == M_INVALID)
- return "Unknown method type for Script";
- else
- m->scripted[methnum] = script;
+ }
+ else if (methnum == M_INVALID) {
+ methnum = ap_method_register(cmd->pool, method);
+ }
+ m->scripted[methnum] = script;
m->configured = 1;
return NULL;
