Bug 41114 - ACL HTTP method is rejected by mod_proxy_ajp
Summary: ACL HTTP method is rejected by mod_proxy_ajp
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_proxy (show other bugs)
Version: 2.2.11
Hardware: Other All
: P2 blocker with 1 vote (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2006-12-06 03:51 UTC by Raymond Bourges
Modified: 2018-11-07 21:09 UTC (History)
3 users (show)

patch against 2.2.11 (1.64 KB, patch)
2009-04-30 22:49 UTC, jstaka
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Raymond Bourges 2006-12-06 03:51:24 UTC
With a WebDAV client when I use ACL method mod_proxy_ajp says to me :

[Wed Dec 06 10:49:47 2006] [error] ajp_marshal_into_msgb - No such method ACL
[Wed Dec 06 10:49:47 2006] [error] ajp_send_header: ajp_marshal_into_msgb failed
[Wed Dec 06 10:49:47 2006] [error] (120010)APR does not understand this error
code: proxy: AJP: request failed to 129.20.999.999:9596 (host.domain.fr)


FYI: I correct this with a patch on ajp_header.c :

--- ajp_header.c.ori	2006-12-06 10:54:59.000000000 +0100
+++ ajp_header.c	2006-12-06 11:14:04.000000000 +0100
@@ -159,7 +159,7 @@
-    0                       /* M_INVALID */
+    SC_M_ACL
 static int sc_for_req_method_by_id(int method_id)
Comment 1 Eirikur Sveinn Hrafnsson 2008-05-07 09:52:54 UTC
This is still a problem in apache 2.2.8 !

Also missing is webdav SEARCH so basic webdav is broken.

best regards
Eirikur Hrafnsson
Chief Software Engineer 
Idega Software
Comment 2 Eirikur Sveinn Hrafnsson 2008-05-07 12:16:08 UTC
We found out why SEARCH method does not work and know how to fix it for now.

The problem is that M_INVALID that is used to limit which methods are allowed is defined in httpd.h and has the value 26, SEARCH HTTP METHOD gives the value 28 into the method sc_for_req_method_by_id(..) so it won't work. Comparing method_id to positions in an array is at best dubious coding. mod_jk uses some other way to do this and mod_dav obviously since they do work.

The fix:
Edit ajp_header.c under modules/proxy

line 161 in Apache 2.2.8
     0                       /* M_INVALID */

remove that last 0 /* M_INVALID */ line
and add instead:
    SC_M_SEARCH /* needs to be the 28 in the array...*/

and in the method:
static int sc_for_req_method_by_id(request_rec *r)

 if (method_id < 0 || method_id > M_INVALID) {

    if (method_id < 0 || method_id > 28) {

Where 28 is the size of the methods array we just added to in the beginning.

Then compile apache again using for example:
> ./configure --prefix=/usr/local/apache2 --enable-mods-shared="all proxy proxy-ajp proxy-balancer filter deflate expires ssl rewrite mime-magic mem-cache info disk-cache dav dav-fs dav-lock" --with-mpm=worker 
> make 
> make install

Eirikur S. Hrafnsson and Pall Helgason
Idega Software

Comment 3 jstaka 2009-04-30 22:49:52 UTC
Created attachment 23567 [details]
patch against 2.2.11

I think this is still a problem in apache 2.2.11.
This patch assigns a id to ACL method.

Comment 4 Grzegorz Turski 2012-04-18 09:58:50 UTC
6 years passed, but this bug is still relevant, even with 2.2.22.

It forces us to use mod_jk to access apache jackrabbit based webDAV, due invalid  ACL and SEARCH method handling.

Comment 5 Raymond Bourges 2012-04-19 08:06:41 UTC
Same thing here ! bug is still present.

We now use mod_proxy_http
Comment 6 Stefan Fritsch 2012-04-20 12:06:42 UTC
The patches in this PR are unfortunately not correct:

SEARCH is registered using ap_method_register() by mod_dav. This means the actual number assigned to SEARCH depends on the module loading order. Adding SEARCH and ACL to httpd itself is a good idea, but in stable releases like 2.2.x and 2.4.x, the M_INVALID number must not change.
Comment 7 William A. Rowe Jr. 2018-11-07 21:09:52 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.