medusa and apache proxy -more info
Tue, 17 Apr 2001 15:25:09 -0000
I don't know if this will lead to anything better but I have had some
problems with apache proxy server too.
I've built an html chat system over medusa and it works fine, but on
our network, if my clients connect through an apache proxy it
does not work as expected. The proxy seems to buffer a lot of data
before transmitting it to the client. This behaviour has only been
observed on apache proxy, no other proxy makes the system fail till
--- In medusa@y..., rprice@u... wrote:
> With more testing we've found out that medusa works differenetly on
> Solaris (sunOS5) and Linux (I'm using Mandrake 7.1) at least when
> using the Linux telnet client:
> On solaris using telnet the server closes the connection immediately
> after the </HTML> when using HTTP/1.0. When using HTTP/1.1 it will
> keep connected. Both as expected.
> On linux the Medusa server will wait 30 seconds before closing the
> session when using HTTP/1.0 and keeps the connection open much
> using HTTP/1.1.
> I've done these tests on Medusa versions 3.39 and 3.19 on linux and
> ONLY on 3.19 on sunOS5.
> --- In medusa@y..., Sam Rushing <rushing@n...> wrote:
> > rprice@u... wrote:
> > > When a user accesses medusa directly (not through a proxy) it
> takes less than 1
> > > second to display the page.
> > >
> > > When a user accesses the same medusa server page via an apache
> proxy server, the
> > > pages seem to hang at 66% loaded. It can then take anywhere
> 2 to 60
> > > seconds for the page to finally load. Another problem when
> accessing through
> > > the proxy is that the browser occasionally indicates 'contacting
> server' for
> > > many seconds before any information is transmitted.
> > >
> > > Any ideas why this would happen?
> > None yet... a couple of things to try:
> > 1) what happens if you try squid instead of apache proxy?
> > 2) what protocol versions (i.e., http/1.0 or 1.1) are being used
> between browser,
> > proxy, and medusa?
> > -Sam