mod_proxy_fcgi: Don't segfault when failing to connect to the backend.
now understood why users haven't reported the segfault (yet) when mod_proxy_fcgi
can't connect to the application
Submitted by: trawick
Reviewed/backported by: jim
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@
1592998 13f79535-47bb-0310-9956-
ffa450edef68
Changes with Apache 2.4.10
+ *) mod_proxy_fcgi: Don't segfault when failing to connect to the backend.
+ (regression in 2.4.9 release) [Jeff Trawick]
+
*) mod_authn_socache: Fix crash at startup in certain configurations.
PR 56371. (regression in 2.4.7) [Jan Kaluza]
PATCHES ACCEPTED TO BACKPORT FROM TRUNK:
[ start all new proposals below, under PATCHES PROPOSED. ]
- * mod_proxy_fcgi: Don't crash when connect to the backend fails.
- trunk patch: http://svn.apache.org/r1590437 (and additional CHANGES tweak in r1592500)
- 2.4.x patch: trunk patch works other than CHANGES
- +1: trawick, covener, ylavic
-
* mod_expires: don't add Expires header to error responses (4xx/5xx),
be they generated or forwarded. PR 55669.
trunk patch: http://svn.apache.org/r1584430
int status;
char server_portstr[32];
conn_rec *origin = NULL;
- proxy_conn_rec *backend;
+ proxy_conn_rec *backend = NULL;
proxy_dir_conf *dconf = ap_get_module_config(r->per_dir_config,
&proxy_module);