Re: TomcatMonitor

2002-06-15 Thread Cliff Woolley

On Sat, 15 Jun 2002, Mladen Turk wrote:

> As a maker of ApacheMonitor I _know_ that the support for the Tomcat's
> start/stop/monitor would be trivial.
> The question is can we (Apache2 and Tomcat) agree to coexist, or make
> two different try buttons.

I wouldn't have a problem with that.  No sense reinventing the wheel for
one or the other of us...  +1.

--Cliff


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 




RE: Apache 2.0.18 problem with mod_jk and

2001-06-11 Thread Cliff Woolley

On Mon, 11 Jun 2001, GOMEZ Henri wrote:

> Thomas Bezdicek suggested me to use BrowserMatch :
>
> I add that in httpd.conf of AP 2.0.16 :
>
> BrowserMatch "MSIE 5.5;" nokeepalive downgrade-1.0 force-response-1.0
>
> Now IE5 works but it is normal to make this kind of hack
> for mod_jk ?

Well, it's not specific to mod_jk... hacks like this are pretty much
required in mod_ssl, for example.  And it's not just "MSIE 5.5" for
mod_ssl... you might find that you need to do something similar for ALL
versions of IE.

Anyway, since you've verified that the problem still exists in 2.0.16,
it's not the bucket lifetime bug I mentioned earlier... but since this
approach works, we can blame it on more IE absurdity and call it a day.

--Cliff


----------
   Cliff Woolley
   [EMAIL PROTECTED]
   Charlottesville, VA





Re: Apache 2.0.18 problem with mod_jk and

2001-06-09 Thread Cliff Woolley

On Fri, 8 Jun 2001, GOMEZ Henri wrote:

> I've got some problems with Apache 2.0.18 and mod_jk
> with Internet Explorer 5.5 and Mozilla 0.8.1.
>
> Even if there is a network traffic (I attached the
> ethereal logs (tcpdump compatible)), I couldn't get
> the Tomcat pages.

I'm not positive, but I'd wager a guess that this is probably related to
the bucket lifetime bug that appeared in Apache after 2.0.16 and has been
discussed at some length on new-httpd and apr-dev.  It's halfway fixed in
CVS.

Anyway, if you didn't see this problem with 2.0.16 and did with 2.0.18,
that's almost certainly what's going on.

--Cliff


------
   Cliff Woolley
   [EMAIL PROTECTED]
   Charlottesville, VA