need examples for mod_jk/mod_jk2 conf and properties

[Henri Gomez]

Hi to all,

I'll need examples files for mod_jk 1.2.0 and 2.0.0beta for the
tomcat-connectors rpm I'm working on.

mod_jk 1.2.0 is well know but there is new features like failover only mode in
Load-Balancing (don't remember the exact synthax). Also we need to comment the
new JkOption ForwardDirectory.

mod_jk 2.2.0 is more new and I'd like to have a full workers2.properties files
with all latest features.

Thanks for your help :)



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

Re: AJP13,Tomcat404 and SSL

[Henri Gomez]

Quoting Gernot Lepuschitz <[EMAIL PROTECTED]>:

> As i mentioned last time, i´m writing an AJP Client for our
> server. Now that ajp13 supports ssl, I want to implement it, too. But
> I don´t really understant how this will work. 

ajp13 supports SSL ATTRIBUTES, but don't make use of SSL, so it's not a secure
protocol. I proposed sometimes ago to add in ajp14 (or ajp13++) some sort of
crypto but it was not selected because it will add delay and sus slow the
througput between Apache and Tomcat. Better to use a SSH tunnel between your
AJP13 client and server (it's native code and fast).

> I first thought about an Inet-socket-ssl connection to Tomcat where
> the whole AJP Request will be ssl encrypted. But then I remembered the
> isssl flag within the AJP Protocol, so I thought, that maybe only the
> http headers are ssl encrypted (somekind of tunneling the http headers
> from the browser to Tomcat without decryption between). But that won´t
> work because I have to encode the Strings of the http headers
> (key,value).

isssl only indicate that the request came from a SSL connection.

Regards

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

RE: AJP13,Tomcat404 and SSL

[Kevin Seguin]

the ajp13 protocol does not support ssl.  the "isssl" flag you are refering to is 
probably the ajp request attribute that indicates whether or not the request to the 
web server was using https.

> -Original Message-
> From: Gernot Lepuschitz [mailto:[EMAIL PROTECTED]] 
> Sent: Thursday, August 22, 2002 7:59 AM
> To: [EMAIL PROTECTED]
> Subject: AJP13,Tomcat404 and SSL
> 
> 
> As i mentioned last time, i´m writing an AJP Client for our 
> server. Now that ajp13 supports ssl, I want to implement it, 
> too. But I don´t really understant how this will work. 
> 
> I first thought about an Inet-socket-ssl connection to Tomcat 
> where the whole AJP Request will be ssl encrypted. But then I 
> remembered the isssl flag within the AJP Protocol, so I 
> thought, that maybe only the http headers are ssl encrypted 
> (somekind of tunneling the http headers from the browser to 
> Tomcat without decryption between). But that won´t work 
> because I have to encode the Strings of the http headers (key,value).
> 
> So, could you tell me how it works?
> 
> Many thanks,
> 
> Gernot
> 
> --
> To unsubscribe, e-mail:   
>  [EMAIL PROTECTED]>
> For 
> additional commands, 
> e-mail: 
> 
> 
> 

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

DO NOT REPLY [Bug 11934] New: - web.xml security-constraint is parsed incorrectly

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11934

web.xml security-constraint is parsed incorrectly

   Summary: web.xml security-constraint is parsed incorrectly
   Product: Tomcat 4
   Version: 4.1.9
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Here's the definition from 2.3 spec:



With the display-name defined we have:

SEVERE: Parse Error at line 84 column -1: Element "security-constraint" does not
allow "display-name" here.
org.xml.sax.SAXParseException: Element "security-constraint" does not allow
"display-name" here.
at org.apache.crimson.parser.Parser2.error(Parser2.java:3160)
at
org.apache.crimson.parser.ValidatingParser$ChildrenValidator.consume(ValidatingParser.java:349)
at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1317)
at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)
at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)
at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)
at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)
at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:500)
at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)
at org.apache.commons.digester.Digester.parse(Digester.java:1284)
at
org.apache.catalina.startup.ContextConfig.applicationConfig(ContextConfig.java:282)
  
at ...

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

DO NOT REPLY [Bug 11933] New: - every time u go to the server u get the default incoding

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11933

every time u go to the server u get the default incoding

   Summary: every time u go to the server u get the default incoding
   Product: Tomcat 3
   Version: Unknown
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Critical
  Priority: Other
 Component: Encoding
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


I have a jsp page which I set up its encoding
<%@ page contentType="text/html;charset=WINDOWS-1255"%>
if this page does not need to load anything elese like images style sheet etc 
the encoding passed the the Tomcat will stay WINDOWS-1255 but if the page loads
an image or a style sheet etc the encoding sent to the tomcat on submit will be 
the default ISO8859-1 

please help

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

DO NOT REPLY [Bug 11931] New: - incorrect parsing inside jsp:include

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11931

incorrect parsing inside jsp:include

   Summary: incorrect parsing inside jsp:include
   Product: Tomcat 4
   Version: 4.1.9
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Major
  Priority: Other
 Component: Jasper 2
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Inside jsp:include "value" attribute the parser failed to recognize 2
consecutive expressions:

<% String x = "abc"; String y = "def"; %>




Relevent protion of the bug_jsp.java:
...
String x = "abc"; String y = "def";  out.write("\r\n\r\n");
JspRuntimeLibrary.include(request, response, "nothing.jsp" + "?" + "param_name="
+ java.net.URLEncoder.encode( x %><%= y ), out, false);
...

"x %><%= y" is really not what one expects to find there.

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

AJP13,Tomcat404 and SSL

[Gernot Lepuschitz]

As i mentioned last time, i´m writing an AJP Client for our
server. Now that ajp13 supports ssl, I want to implement it, too. But
I don´t really understant how this will work. 

I first thought about an Inet-socket-ssl connection to Tomcat where
the whole AJP Request will be ssl encrypted. But then I remembered the
isssl flag within the AJP Protocol, so I thought, that maybe only the
http headers are ssl encrypted (somekind of tunneling the http headers
from the browser to Tomcat without decryption between). But that won´t
work because I have to encode the Strings of the http headers
(key,value).

So, could you tell me how it works?

Many thanks,

Gernot

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

DO NOT REPLY [Bug 11929] New: - JDBC Realm rejects user at first login

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11929

JDBC Realm rejects user at first login

   Summary: JDBC Realm rejects user at first login
   Product: Tomcat 4
   Version: 4.0.4 Final
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


I have set up a JDBC Realm working normally so far. But after a certain amount 
of time I have the problem that the realm rejects the login sending my own 
login error page saying the log in is incorrect. This mostly happens overnight, 
when there was no traffic for hours. Then the first login is always incorrect, 
even though the entered values are valid.

After that I have no probs logging in.

bye
Michael Thelen

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

RE: Jasper 2 class files

[John Trollinger]

This would be an easy change to JspC so that you could have a flag that
would generate package names instead of using the standard package name.

If there is any interest in this let me know..

 

-Original Message-
From: Steve Downey [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, August 21, 2002 8:00 PM
To: Tomcat Developers List
Subject: RE: Jasper 2 class files

However, in the context of JspC, it's a problem to map them to the same
package and class name. The custom URLClassLoader works within the JSP
engine, but the general servlet class loader doesn't know about those
rules.
So when it sees those entries in web.xml, it will map all hello.jsp
files,
no matter where they reside, to org.apache.jsp.hello_jsp.



> -Original Message-
> From: Glenn Nielsen [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 21, 2002 7:54 PM
> To: Tomcat Developers List
> Subject: Re: Jasper 2 class files
>
>
> Yes, you can have two JSP pages with the same name but in
> different directories
> and everything will work fine even though they have the same
> package and class name.
> This is because a custom URLClassLoader is created for each
> individual JSP page.
> That class loader only loads the one java class for that one JSP page.
>
> For example:
>
> /myapp/this/hello.jsp
> /muapp/that/hello.jsp
>
> The class files will end up in:
>
> $CATALINA_BASE/work/Standalone/localhost/myapp/this/hello.class
> $CATALINA_BASE/work/Standalone/localhost/myapp/that/hello.class
>
> Since two different URLClassLoaders are used Jasper can
> load each of the above two classes even though they have
> the same package and class name.
>
> The old methods Jasper used for loading java classes generated for JSP
> pages was very inefficient.  The above change simplified Jasper and
> improved its performance by 25%.
>
> Regards,
>
> Glenn
>
> John Trollinger wrote:
> > Greg,
> >
> > I took this off of the bug tracking because it is not a bug and I
> > thought there are people a lot smarter than me in this mailing list
that
> > could help answer you questions.
> >
> > I do not know how jasper differentiates between hello.jsp and
> > /anydir/hello.jsp when the both compile to a class
> > org.jasper.jsp.hello_jsp but it does work...
> >
> > My hello.jsp in the root dir prints hello Jasper world and my
hello.jsp
> > in the subdir prints hello john world.  It works without a hitch..
> > (notice that I have removed the .java files for the 2 hello world
files
> > and it did not regenerate them)
> >
> > Here is my file list
> >
> > Directory of C:\appserver\Tomcat\jspcache
> >
> > 08/21/2002  02:19 PM  .
> > 08/21/2002  02:19 PM  ..
> > 08/21/2002  11:47 AM 3,496 date_jsp.java
> > 08/21/2002  11:52 AM 2,975 hello_jsp.class
> > 08/21/2002  11:51 AM 2,883 index_jsp.class
> > 08/21/2002  11:51 AM 1,863 index_jsp.java
> > 08/21/2002  01:27 PM  subdir
> >4 File(s) 11,217 bytes
> >
> >  Directory of C:\appserver\Tomcat\jspcache\subdir
> >
> > 08/21/2002  01:27 PM  .
> > 08/21/2002  01:27 PM  ..
> > 08/21/2002  11:47 AM 3,334 date2_jsp.java
> > 08/21/2002  11:52 AM 2,970 hello_jsp.class
> >
> > Here is my jsp.xml
> >
> > 
> >
> > 
> > org.apache.jsp.date_jsp
> > org.apache.jsp.date_jsp
> > 
> >
> > 
> > org.apache.jsp.hello_jsp
> > org.apache.jsp.hello_jsp
> > 
> >
> > 
> > org.apache.jsp.date2_jsp
> > org.apache.jsp.date2_jsp
> > 
> >
> > 
> > org.apache.jsp.hello_jsp
> > org.apache.jsp.hello_jsp
> > 
> >
> > 
> > org.apache.jsp.date_jsp
> > /date.jsp
> > 
> >
> > 
> > org.apache.jsp.hello_jsp
> > /hello.jsp
> > 
> >
> > 
> > org.apache.jsp.date2_jsp
> > /subdir/date2.jsp
> > 
> >
> > 
> > org.apache.jsp.hello_jsp
> > /subdir/hello.jsp
> > 
> >
> > 
> >
> >
> > --
> > To unsubscribe, e-mail:
> 
> > For additional commands, e-mail:
> 
>
>
>
>
> --
> To unsubscribe, e-mail:
> 
> For additional commands, e-mail:
> 
>
>
>


--
To unsubscribe, e-mail:

For additional commands, e-mail:



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

Re: tomcat 4.1.9 rpms available

[Bojan Smojver]

Legend!

Bojan

On Thu, 2002-08-22 at 18:37, Henri Gomez wrote:
> The TC 4.1.9 beta rpms are available :
> 
> http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.9-beta/rpms/
> 
> Nota that we share now the rpms with the jpackage project (www.jpackage.org), so
> for those of you who want to rebuild source rpms, you should go to jpackage site
> to get the required rpms.
> 
> Enjoy


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

DO NOT REPLY [Bug 11919] New: - Can't create servlet-mapping of "/" (not "/*")

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11919

Can't create servlet-mapping of "/" (not "/*")

   Summary: Can't create servlet-mapping of "/" (not "/*")
   Product: Tomcat 4
   Version: 4.0.4 Final
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Webapps:Administration
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


web.xml:

--begin--

http://java.sun.com/dtd/web-app_2_3.dtd";>

  
Demo
Demo
  

  
Demo
/
  

--end--

I would like to map "http://host/context"; to the Demo servlet by using the 
above web.xml.  But, it seems that all the request to the above context will be 
map to Demo too (e.g., http://host/context/foo.html will be map to Hello too)!  
The "/" url-pattern just act like "/*".

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

tomcat 4.1.9 rpms available

[Henri Gomez]

The TC 4.1.9 beta rpms are available :

http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.9-beta/rpms/

Nota that we share now the rpms with the jpackage project (www.jpackage.org), so
for those of you who want to rebuild source rpms, you should go to jpackage site
to get the required rpms.

Enjoy





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