Jim Jagielski [EMAIL PROTECTED] writes:
Can you try HEAD on httpd-trunk for a fix until something
more robust as far as the connections are implemented...
It gets the backend-connections right, but segfaults in the new code in
proxy_util.c.
I got the following out of a coredump:
dbx:
-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,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I briefly tried httpd-2.1.10 today and still see this.
(Same httpd.conf, only changed ServerRoot to
/usr/local/apache2-2.1.10/)
kind regards
Hansjörg
Hansjoerg Pehofer [EMAIL PROTECTED] writes:
Hi,
I experienced Apache-2.1.7 (/w WorkerMPM
Hi,
I experienced Apache-2.1.7 (/w WorkerMPM on Solaris 9) connecting to the
wrong backends when having configured more than one balancer cluster.
(see httpd.conf below)
ErrorLog shows some odd entries (marked in the example below) during
proxy_util.c's ap_proxy_determine_connection().
I could
On Thu, Jul 07, 2005 at 09:22:25PM +0200, [EMAIL PROTECTED] wrote:
Have you checked
http://mail-archives.apache.org/mod_mbox/httpd-dev/200504.mbox/[EMAIL
PROTECTED] ?
It contains a small patch which was not discussed any further here.
Hi,
i tried your patch today. Unfortunately
Hi,
it has been some time since the original thread.
This is in reply to [1].
Sander Striker wrote:
[EMAIL PROTECTED] wrote:
The problem seems to be, that the proxied backend server that is
cached via mod_disk_cache originally
delivers HTTP status 301 and the Location
