tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Justin Erenkrantz <jerenkra...@ebuilt.com>
Subject Re: [tomcat-dev] [J-T-C] What about ajp13 refactory in java ?
Date Tue, 19 Jun 2001 16:42:40 GMT
On Tue, Jun 19, 2001 at 06:16:15PM +0200, Gomez Henri wrote:
> webapp: mod_webapp/warp protocol (only ajp14)

( Fodder for a STATUS file... )

FWIW, redirects are broken with mod_webapp.  This is due to the fact
that mod_webapp isn't passing enough information to the Java side about
the requested URL (it seems to be only passing in the path - i.e. 
/index.html).  

Warp looks like it needs to know about the scheme, host, port, etc.
This is causing problems in the
javax.servlet.http.HttpUtils.getRequestURL code because there is no
scheme, host, port, etc.  

java.lang.NullPointerException 
    at javax.servlet.http.HttpUtils.getRequestURL(HttpUtils.java:338)
    at org.apache.catalina.connector.HttpResponseBase.toAbsolute(HttpResponseBase.java:669)
    at org.apache.catalina.connector.HttpResponseBase.sendRedirect(HttpResponseBase.java:1072)
    at org.apache.catalina.connector.HttpResponseFacade.sendRedirect(HttpResponseFacade.java:150)

I'm thinking that Apache httpd can just pass along all of the URL
information it has.  But, will warp be able to handle it?  So, instead
of passing /index.html, pass http://foo.example.com/index.html as the
URL?

I will try to take a look at this, but if someone with more knowledge 
can take a look at it and beat me to it, I'd appreciate it.  -- justin


Mime
View raw message