-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rüdiger, Jim,
I used the tarball from http://people.apache.org/~pquerna/dev/httpd-2.1.10/. Ruediger Pluem <[EMAIL PROTECTED]> writes: [...] > > I think the real problem happens if you have requests to different backends > (webapp-cluster, axkit-cluster) on one > shared keepalive connection to the reverse proxy. > > So having something like > > GET /library/q > and > GET /anything > > served over the same keepalive connection between client and reverse proxy > should cause trouble, because of > > if (!r->main) { > backend = (proxy_conn_rec *) ap_get_module_config(c->conn_config, > &proxy_http_module); > } > > starting at line 1668 of mod_proxy_http.c which gets the previous backend > connection. Although the socket to the backend is closed for Reverse Proxy > Requests > in ap_proxy_determine_connection of line 1856 of proxy_util.c, the new > connection > gets created to the same address in line 2010 of proxy_util.c > (ap_proxy_connect_backend). > I have not found the time to search for a solution. > Just as a check to my theory can you disable keepalives and see if everything > works correctly > then? You are right, it works correctly with KeepAlive Off. Thanks, Hansjörg - -- IT Services University of Innsbruck CFB4 D6E7 33F4 34C0 18B9 6661 E355 4337 3F8B D9C2 http://purl.org/net/hansjoerg.pehofer/public_key -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDgw5G41VDNz+L2cIRAj7RAJ9JCAD37QsNd2I7tGuDIFaAao61qACdGUq0 ZgtLXEkd3TBZ5gM+CJmyyRU= =eYuY -----END PGP SIGNATURE-----
