[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: apache22 forward/reverse proxy on current
On Mon, 16 Jun 2008 03:49:51 pm Sarton O'Brien wrote:
> Hi all,
> Updated an i386pae domu to amd64 and in the process updated apache22 to the
> Since having done the above, apache serves as it should but when proxying a
> connection it fails with no errors produced and only severed connections as
> indication there is a problem:
> [Mon Jun 16 12:34:18 2008] [debug] proxy_util.c(2015): proxy:
> connected /search?hl=en&q=test&btnG=Google+Search&meta= to
> [Mon Jun 16 12:34:18 2008] [debug] proxy_util.c(2172): proxy: HTTP: fam 2
> socket created to connect to *
> [Mon Jun 16 12:34:18 2008] [debug] proxy_util.c(2269): proxy: HTTP:
> complete to 184.108.40.206:80 (www.google.com.au)
> [Mon Jun 16 12:34:18 2008] [debug] mod_proxy_http.c(1622): proxy: start body
> [Mon Jun 16 12:34:28 2008] [info] [client 192.168.16.211] (32)Broken pipe:
> core_output_filter: writing data to the network
> [Mon Jun 16 12:34:28 2008] [debug] mod_proxy_http.c(1711): proxy: end body
> [Mon Jun 16 12:34:28 2008] [debug] proxy_util.c(1873): proxy: HTTP: has
> released connection for (*)
> I typically use it to proxy internal client connections and to serve inbound
> requests to a zope server.
> The symptoms at present are the ability to access google via a client
> but the inability to query google (as shown above) with the connection being
> severed pretty quickly.
> Accessing the zope server results in the title being displayed but that's
> about it.
I lie. After letting it sit for about half an hour it did actually load the
page. So it does eventually serve the zope instance if you wait.
For a demo of the brokenness visit roguewrt.org
Main Index |
Thread Index |