Return consistent error status for proxy unable to connect
PR 46971
Submitted by: niq
Reviewed/backported by: jim
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@882153
13f79535-47bb-0310-9956-
ffa450edef68
control is still vulnerable, unless using OpenSSL >= 0.9.8l.
[Joe Orton, Ruediger Pluem]
+ *) Proxy: unable to connect to a backend is SERVICE_UNAVAILABLE,
+ rather than BAD_GATEWAY or (especially) NOT_FOUND.
+ PR 46971 [evanc nortel.com]
+
*) mod_charset_lite: Honor 'CharsetOptions NoImplicitAdd'.
[Eric Covener]
PATCHES ACCEPTED TO BACKPORT FROM TRUNK:
[ start all new proposals below, under PATCHES PROPOSED. ]
- * proxy: return consistent error message in case of failure to
- connect to backend.
- PR 46971
- Patch: http://svn.apache.org/viewvc?rev=806920&view=rev
- +1: niq, covener, jim
PATCHES PROPOSED TO BACKPORT FROM TRUNK:
return DECLINED;
}
else {
- return HTTP_BAD_GATEWAY;
+ return HTTP_SERVICE_UNAVAILABLE;
}
}
/* Step Two: Make the Connection */
if (ap_proxy_connect_backend(proxy_function, backend, worker, r->server)) {
- if (r->proxyreq == PROXYREQ_PROXY)
- status = HTTP_NOT_FOUND;
- else
- status = HTTP_SERVICE_UNAVAILABLE;
+ status = HTTP_SERVICE_UNAVAILABLE;
goto cleanup;
}