Martin Kraemer wrote:
> > (192.168.69.1) (pgtm0035)
> > client <--> Apache-1.3.13 <--> Apache-1.3.24
> >Proxy Proxy *and*
> > Origin Server
One question: in the above senario, where is the data coming from? Is
there anoth
Martin Kraemer wrote:
> Still, we get chunked encoding where the client never expressed the wish
> (or capability) to handle it.
As far as I understand, the decision to chunk (or not) is handled within
buff.c - seems proxy is not signalling buff.c correctly on what the
protocol level is on the c
Martin Kraemer wrote:
>
> Jim: Sorry I notice this so late :-( Only in this special combination does
> the bug happen.
>
No problem. Let me look into it. Worse-comes-to-worse, we announce
a patch-file (ala the pthread stuff with 1.3.23 and Solaris)
and work towards a 1.3.25 in a few weeks. I m
On Fri, Mar 22, 2002 at 10:38:05PM +0100, Kraemer, Martin wrote:
>
> No, even worse: I now have two Apache-1.3.24 copies in a proxy chain.
What I tried:
SetEnv force-response-1.0 1
SetEnv downgrade-1.0 1
but it didn't change anything... Even when set on both servers.
Jim:
Martin Kraemer wrote:
>
> No, even worse: I now have two Apache-1.3.24 copies in a proxy chain.
> Same behavior:
>
> Still, we get chunked encoding where the client never expressed the wish
> (or capability) to handle it.
>
G... and the 1.3.24 announcement is already out :/
--
==
On Fri, Mar 22, 2002 at 09:40:44PM +0100, Kraemer, Martin wrote:
>
> (192.168.69.1) (pgtm0035)
> client <--> Apache-1.3.13 <--> Apache-1.3.24
>Proxy Proxy *and*
> Origin Server
No, even worse: I now have two Apache-1.3.24
On Thu, Mar 21, 2002 at 04:04:53PM -0800, Roy T. Fielding wrote:
> Tarball tested on RH Linux 2.2.16-22 with no problems. +1
>
> Roy
I just notice that there are problems with the proxy.
They manifest in a combination of an "old" proxy (Apache/1.3.13-dev)
and the new proxy (Apache/1.3.24) i
