Even in Ajp13 there is still a bug.
In the API docs for javax.servlet.ServletRequest.getRequestDispatcher it
says
"The pathname specified may be relative, although it cannot extend outside
the current servlet context. If the path begins with a "/" it is interpreted
as relative to the current
neither of the above functions work properly when I am using a non standard
port for https (ex: 445 instead of 443)
Apache 1.3.14
Tomcat 3.2.1 + mod_jk.so
Open SSL 0.9.6
mod_ssl 2.7.?-1.3.14
any idea why this is happening?
Filip
~
Namaste - I bow to the divine in you.
~
Filip Hanik
Technical
Filip,
Which connection protocol are you using? ajp12? ajp13? jserv?
-Dan
Filip Hanik wrote:
neither of the above functions work properly when I am using a non standard
port for https (ex: 445 instead of 443)
Apache 1.3.14
Tomcat 3.2.1 + mod_jk.so
Open SSL 0.9.6
mod_ssl
ajp12
should I try ajp13?
Filip
~
Namaste - I bow to the divine in you.
~
Filip Hanik
Technical Architect
[EMAIL PROTECTED]
- Original Message -
From: "Dan Milstein" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, January 19, 2001 4:18 PM
Subject: Re: sendRedirect, include and
this is what happens, the sendRedirect or include or forward switches the
url from saying https to say http even though the port is http
/Filip
Bad Request
Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
I don't know if that will fix the problem, but if you could try that (i.e. using ajp13
and seeing if you still have this problem), that would definitely help me narrow this
down (and since there seem to be some basic redirect problems in TC 3.2 / mod_jk, that
would be very, very helpful).
Good catch,
it works fine with the Ajp13 protocol.
so now we know where the problem is. thanks a lot for your help
Filip
~
Namaste - I bow to the divine in you.
~
Filip Hanik
Technical Architect
[EMAIL PROTECTED]
- Original Message -
From: "Dan Milstein" [EMAIL PROTECTED]
To: [EMAIL
