Tomcat 3.2.2 beta 4 & mod_ssl & URI

[Wolle <wo...@dorf.RWTH-Aachen.DE>]

Hello,
i have one question about the session tracking (URI) with mod_ssl.
You have said, that you have fixed it.
But in TC3.2.2b4 it isn't fixed, did you mean you fixed it only in the final
release ?
I think session tracking and mod_ssl is some important thing, that should work
together.

Please worte back,
Michael

Re: Tomcat 3.2.2 beta 4 & mod_ssl & URI

[Wolle <wo...@dorf.RWTH-Aachen.DE>]

I have testet the TC3.2.2b4 now with the ajp13 protocol over the new
mod_jk-eapi.so
and mod_jk-stdapi.so (release 4/30), and nothing will work with URI Rewriting.
Have I  something more to  do ? set TOMCAT_OPS like below, or to copy the
jsee.jar and jnet.jar in the lib dir ?

Greetings and sorry for the massive questions,
Michael

Marc Saegesser wrote:

> There were two problems that I knew about and both are described in the bug
> report http://nagoya.apache.org/bugzilla/show_bug.cgi?id=578.  One problem
> is addressed by defining
> java.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol and other
> problem was that it wouldn't set the default port correctly for https URLs.
>
> Both of these bugs have been fixed in beta 4.  If your still seeing a
> problem there must be something else wrong that I haven't seen yet.  One
> thing to note, however, is that there is a known issue with AJP12 that
> prevents URL rewritting from working correctly on ports other than 443.  For
> example, if your using Apache to serve HTTPS on port 8443 then Tomcat won't
> know that the connection is secure and will think the URL scheme is actually
> HTTP.  This is a limitation of the AJP protocol and we can't fix it.  The
> AJP13 protocol does not have this problem.
>
> > -----Original Message-----
> > From: Wolle [mailto:wolle@dorf.RWTH-Aachen.DE]
> > Sent: Tuesday, May 01, 2001 2:55 PM
> > To: tomcat-dev@jakarta.apache.org
> > Subject: Tomcat 3.2.2 beta 4 & mod_ssl & URI
> >
> >
> > Hello,
> > i have one question about the session tracking (URI) with mod_ssl.
> > You have said, that you have fixed it.
> > But in TC3.2.2b4 it isn't fixed, did you mean you fixed it only
> > in the final
> > release ?
> > I think session tracking and mod_ssl is some important thing,
> > that should work
> > together.
> >
> > Please worte back,
> > Michael
> >

RE: Tomcat 3.2.2 beta 4 & mod_ssl & URI

[Marc Saegesser <ma...@apropos.com>]

There were two problems that I knew about and both are described in the bug
report http://nagoya.apache.org/bugzilla/show_bug.cgi?id=578.  One problem
is addressed by defining
java.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol and other
problem was that it wouldn't set the default port correctly for https URLs.

Both of these bugs have been fixed in beta 4.  If your still seeing a
problem there must be something else wrong that I haven't seen yet.  One
thing to note, however, is that there is a known issue with AJP12 that
prevents URL rewritting from working correctly on ports other than 443.  For
example, if your using Apache to serve HTTPS on port 8443 then Tomcat won't
know that the connection is secure and will think the URL scheme is actually
HTTP.  This is a limitation of the AJP protocol and we can't fix it.  The
AJP13 protocol does not have this problem.

> -----Original Message-----
> From: Wolle [mailto:wolle@dorf.RWTH-Aachen.DE]
> Sent: Tuesday, May 01, 2001 2:55 PM
> To: tomcat-dev@jakarta.apache.org
> Subject: Tomcat 3.2.2 beta 4 & mod_ssl & URI
>
>
> Hello,
> i have one question about the session tracking (URI) with mod_ssl.
> You have said, that you have fixed it.
> But in TC3.2.2b4 it isn't fixed, did you mean you fixed it only
> in the final
> release ?
> I think session tracking and mod_ssl is some important thing,
> that should work
> together.
>
> Please worte back,
> Michael
>