From 17d779bff4f706b16449c7042c1ee7b0b59a29eb Mon Sep 17 00:00:00 2001 From: Jean-Frederic Clere Date: Thu, 8 Sep 2011 12:41:30 +0000 Subject: [PATCH] Use HTTP_NOT_IMPLEMENTED instead of HTTP_BAD_REQUEST. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1166657 13f79535-47bb-0310-9956-ffa450edef68 --- modules/proxy/mod_proxy_ajp.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/modules/proxy/mod_proxy_ajp.c b/modules/proxy/mod_proxy_ajp.c index 2d4661d4c5..c92cea5833 100644 --- a/modules/proxy/mod_proxy_ajp.c +++ b/modules/proxy/mod_proxy_ajp.c @@ -214,9 +214,11 @@ static int ap_proxy_ajp_request(apr_pool_t *p, request_rec *r, "proxy: AJP: request failed to %pI (%s)", conn->worker->cp->addr, conn->worker->s->hostname); - if (status == AJP_EOVERFLOW || status == AJP_EBAD_METHOD) + if (status == AJP_EOVERFLOW) return HTTP_BAD_REQUEST; - else { + else if (status == AJP_EBAD_METHOD) { + return HTTP_NOT_IMPLEMENTED; + } else { /* * This is only non fatal when the method is idempotent. In this * case we can dare to retry it with a different worker if we are -- 2.40.0