Re: sendRedirect, include and forward don't work with mod_jk and non standard ssl port
Filip Hanik wrote:
>
> 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 context root. This method returns null if the
> servlet container cannot return a RequestDispatcher."
>
> but it turns out that I can't say
> getRequestDispatcher("myhtml.html"); because it throws an array index out of
> bounds exception.
>
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1503)
> at org.apache.tomcat.util.FileUtil.catPath(FileUtil.java:109)
> [...]
> getRequestDispatcher("/myhtml.html"); works fine however.
>
> should I file the bug report, if so where?
Yes, at this URL:
Hans
--
Hans Bergsten [EMAIL PROTECTED]
Gefion Software http://www.gefionsoftware.com
Author of JavaServer Pages (O'Reilly), http://TheJSPBook.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Re: sendRedirect, include and forward don't work with mod_jk and non standard ssl port
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 context root. This method returns null if the
servlet container cannot return a RequestDispatcher."
but it turns out that I can't say
getRequestDispatcher("myhtml.html"); because it throws an array index out of
bounds exception.
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1503)
at org.apache.tomcat.util.FileUtil.catPath(FileUtil.java:109)
at
org.apache.tomcat.facade.HttpServletRequestFacade.getRequestDispatcher(HttpS
ervletRequestFacade.java:322)
at com.ratexchange.presentation.FilipTest.doGet(FilipTest.java:37)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:404)
at org.apache.tomcat.core.Handler.service(Handler.java:286)
at
org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372
getRequestDispatcher("/myhtml.html"); works fine however.
should I file the bug report, if so where?
Filip
~
Namaste - I bow to the divine in you.
~
Filip Hanik
Technical Architect
[EMAIL PROTECTED]
- Original Message -
From: "Filip Hanik" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, January 19, 2001 4:58 PM
Subject: Re: sendRedirect, include and forward don't work with mod_jk and
non standard ssl port
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 PROTECTED]>
Sent: Friday, January 19, 2001 4:46 PM
Subject: Re: sendRedirect, include and forward don't work with mod_jk and
non standard ssl 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).
Thanks.
-Dan
p.s. What browser are you using?
Filip Hanik wrote:
>
> 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 forward don't work with mod_jk and
> non standard ssl port
>
> Filip,
>
> Which connection protocol are you using? ajp12? ajp13? jserv?
>
> -Dan
>
--
Dan Milstein // [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Re: sendRedirect, include and forward don't work with mod_jk and non standard ssl port
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 PROTECTED]> Sent: Friday, January 19, 2001 4:46 PM Subject: Re: sendRedirect, include and forward don't work with mod_jk and non standard ssl 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). Thanks. -Dan p.s. What browser are you using? Filip Hanik wrote: > > 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 forward don't work with mod_jk and > non standard ssl port > > Filip, > > Which connection protocol are you using? ajp12? ajp13? jserv? > > -Dan > -- Dan Milstein // [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: sendRedirect, include and forward don't work with mod_jk and non standard ssl 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). Thanks. -Dan p.s. What browser are you using? Filip Hanik wrote: > > 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 forward don't work with mod_jk and > non standard ssl port > > Filip, > > Which connection protocol are you using? ajp12? ajp13? jserv? > > -Dan > -- Dan Milstein // [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: sendRedirect, include and forward don't work with mod_jk and non standard ssl port
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. Instead use the HTTPS scheme to access this URL, please. Hint: https://rpit.ratexchange.net:9701/ Apache/1.3.14 Server at rpit.ratexchange.net Port 9701 ~ 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 forward don't work with mod_jk and non standard ssl port 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 2.7.?-1.3.14 > > any idea why this is happening? > > Filip > ~ > Namaste - I bow to the divine in you. > ~ > Filip Hanik > Technical Architect > [EMAIL PROTECTED] -- Dan Milstein // [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: sendRedirect, include and forward don't work with mod_jk and non standard ssl port
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 forward don't work with mod_jk and non standard ssl port 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 2.7.?-1.3.14 > > any idea why this is happening? > > Filip > ~ > Namaste - I bow to the divine in you. > ~ > Filip Hanik > Technical Architect > [EMAIL PROTECTED] -- Dan Milstein // [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: sendRedirect, include and forward don't work with mod_jk and non standard ssl port
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 2.7.?-1.3.14 > > any idea why this is happening? > > Filip > ~ > Namaste - I bow to the divine in you. > ~ > Filip Hanik > Technical Architect > [EMAIL PROTECTED] -- Dan Milstein // [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
sendRedirect, include and forward don't work with mod_jk and non standard ssl port
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 Architect [EMAIL PROTECTED] - Original Message - From: "Remy Maucherat" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 19, 2001 3:25 PM Subject: Re: [PROPOSAL] Tomcat 4.0-beta API Change: Security Manager Facades Quoting "Craig R. McClanahan" <[EMAIL PROTECTED]>: > Kurt Schrader wrote: > > > So what do we need a 4.1 branch for then? > > If we take the action Remy recommends, we won't. I'm +1 for this (it > will certainly > reduce the effort of double-committing all the changes), if we're > willing to accept > the fact that it will increase the time before a 4.0 production quality > release is > ready. Given the delay caused by the security manager support inclusion and the Valve modifications, it won't probably cause any additional delay. > The 4.1 branch was originally created because of a "feature freeze" on > 4.0. The > various proposals today are effectively to "unfreeze" the 4.0 branch, so > that some > new functionality (already committed on the 4.1 branch) can get moved > into 4.0 > instead, along with the other proposed changes that would otherwise need > to be posted > to both. > > We can recreate the 4.1 branch at some future point when 4.0 is > refrozen. Agreed. It that case, I suggest that the 4.1 branch be merged back ASAP. Having a non- beta quality web connector in a beta wasn't a good thing anyway, IMO. I wrongly interpreted the proposal on the security manager, as I was answering an email dealing with i18n at the same time (so I'm +1 now). As Kief suggested, I think that no wrapping should occur if no security manager is present (common sense). There is also a code change needed to provide proper i18n support. Instead of putting in a hack in 4.0 to get around one half of the issue, I suggest instead that some code is moved from the connector.http package to the connector package (some buffers, as well as some code which needs to be merged into HttpRequestBase). Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
