bad news
the changelog link has no info for 1.2.14
Jean-frederic Clere wrote:
The Apache Tomcat team is pleased to announce the release of version
1.2.14 of the Apache Tomcat mod_jk web server connector.
Tomcat is the reference implementation of a web application server
which implements
Bad list, you should contact tomcat-dev instead.
BTW, configure is your friend for building jk).
See you soon on tomcat-dev
On Tue, 22 Mar 2005 15:48:09 +0100, Andreas Andersson
<[EMAIL PROTECTED]> wrote:
> Hi!
>
> I'm not sure this is the right list (there wasn't
Hi!
I'm not sure this is the right list (there wasn't a list about mod_jk)
so let me just say sorry already :)
I'm trying to compile mod_jk with the latest src but get the following
error:
BUILD FAILED
/usr/src/jakarta-tomcat-connectors-1.2.8-src/jk/build.xml:161: Warning:
Coul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
El martes, 20 ener, 2004, a las 13:44 Europe/Madrid, Francisco Javier
Fabra Caro escribió:
Hi all!
I'm trying to install the mod_jk with Apache 1.3.27 and Tomcat 4.1.29.
I
Don't do that unless it is a vendor version properly patched. 1
Hi all!
I'm trying to install the mod_jk with Apache 1.3.27 and Tomcat 4.1.29. I
have installed Apache and Tomcat sucessfully, but I'm not able to
compile and/or install the mod_jk connector.
Someone has been able to install the module with this versions of
Apache+Tomcat? Some
[October 11, 2003]
The Tomcat team is pleased to announce the release of version 1.2.5 of the Apache
Tomcat mod_jk web server connector.
Tomcat is the reference implementation of a web application server which implements
the Java Servlet and JavaServer Pages specifications.
mod_jk is a connector
En réponse à "Gonyou, Austin" <[EMAIL PROTECTED]>:
> Yeah sure no problem. I was directed here after discussing the issue
> with a
> couple of httpd guys.
> I've already checked the tomcat mailing list, as well. Plus this is
> _NOT_ a
> tomcat issue. It&
To: '[EMAIL PROTECTED]'
> Subject: RE: Using mod_jk with apache 1.3.20
>
>
> Yeah sure no problem. I was directed here after discussing
> the issue with a
> couple of httpd guys.
> I've already checked the tomcat mailing list, as well. Plus
>
Yeah sure no problem. I was directed here after discussing the issue with a
couple of httpd guys.
I've already checked the tomcat mailing list, as well. Plus this is _NOT_ a
tomcat issue. It's a mod_jk issue.
--
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-796-
On Tue, 21 Aug 2001, Gonyou, Austin wrote:
> Thanks for the response, but I don't know if it answers the question. Let me
> expount a bit and I'll see if it makes things clearer.
>
Could you *please* do your expounding on the correct mailing list?
The GENERAL list is for issues about Jakarta
me
>
>expount a bit and I'll see if it makes things clearer.
>
>I'm using mod_jk to talk to tomcat. By default tomcat's on 8080. When I
>telnet to port 8080,
>the headers report that content-type is text/html. But, when I telnet to
>port 80, (i.e. mod_jk is makin
Thanks for the response, but I don't know if it answers the question. Let me
expount a bit and I'll see if it makes things clearer.
I'm using mod_jk to talk to tomcat. By default tomcat's on 8080. When I
telnet to port 8080,
the headers report that content-type is text/html
Use this:
//
response.setContentType( "text/html" );
PrintWriter pw = response.getWriter( );
pw.writeln( "" );
pw.writeln( "MOD_JK Test" );
pw.writeln( "Here´s my HTML.&q
I keep getting content-type: text/plain when stuff comes back through
mod_jk. How can I change this?
If I view a page with mozilla, I get nothing but non-rendered source.
--
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-796-9023
email: [EMAIL PROTECTED
14 matches
Mail list logo
