Okay, so we're upgrading to Tomcat 6, and we've encountered a difficulty.

In order to keep URLs consistent (for simpler log parsing and for 
cosmetic reasons) the idea is to have a servlet as the controller and a 
JSP for the display, but only ever to have the servlet URL visible to the 
user. As such:

  servlet:  /path/servlet
  jsp:      /path/page.jsp

The main access is through the servlet, and at the appropriate moment the 
user is forwarded to the JSP, using:

  RequestDispatcher dispatcher =
    request.getRequestDispatcher("/path/page.jsp");
  dispatcher.forward(request, response);

Using Tomcat 5.0, I was able, in the JSP, to use (nothing really hard 
coded):

  if (request.getRequestURL().toString().indexOf("page.jsp") != -1) {
    response.sendRedirect("/path/servlet");
    return; 
  }

.... because the request URL was that of the servlet from which the 
forward was called. In Tomcat 6, however, the request URL is that of the 
forward target.

Reading the API, it looks as if this should have been the behaviour all 
along, but that's moot. The question is: How can I prevent direct access 
to the JSP in another way?

Cheers,
-- Robert

Robert Watkins wrote:> > Reading the API, it looks as if this should have been the behaviour all > along, but that's moot. The question is: How can I prevent direct access > to the JSP in another way?Put the JSP under /WEB-INF/.Tom Hawtin

Tom Hawtin <usenet@tackline.plus.com> wrote innews:46794827$0$8754$ed2619ec@ptn-nntp-reader02.plus.net: > Robert Watkins wrote:>> >> Reading the API, it looks as if this should have been the behaviour>> all along, but that's moot. The question is: How can I prevent direct>> access to the JSP in another way?> > Put the JSP under /WEB-INF/.> > Tom Hawtin> Hmmm -- must be something I'm missing, because I get a 404 error:  The requested resource (/path/page.jsp) is not available.Does the forward path have to change?-- Robert

Tom Hawtin <usenet@tackline.plus.com> wrote in
>> Put the JSP under /WEB-INF/.
>>
>> Tom Hawtin

Robert Watkins wrote:
> Hmmm -- must be something I'm missing, because I get a 404 error:
> 
>   The requested resource (/path/page.jsp) is not available.

It is for the correct value of 'path'.

> Does the forward path have to change?

It has to include the WEB-INF/ path node.

Either:

  RequestDispatcher dispatcher =
     request.getRequestDispatcher( "/application/WEB-INF/page.jsp" );

or just

  RequestDispatcher dispatcher =
     request.getRequestDispatcher( "WEB-INF/page.jsp" );

I usually use relative paths (always down from current, never up).

BTW, if you had provided an SSCCE instead of paraphrasing as 'path', 
'page.jsp', etc., you'd have had a much clearer question.  Notice how 
hand-waving over 'path' actually obscured the issue?

-- 
Lew

Robert Watkins wrote:
> Tom Hawtin <usenet@tackline.plus.com> wrote in
> news:46794827$0$8754$ed2619ec@ptn-nntp-reader02.plus.net: 
> 
>> Robert Watkins wrote:
>>> Reading the API, it looks as if this should have been the behaviour
>>> all along, but that's moot. The question is: How can I prevent direct
>>> access to the JSP in another way?
>> Put the JSP under /WEB-INF/.
>>
>> Tom Hawtin
>>
> 
> Hmmm -- must be something I'm missing, because I get a 404 error:
> 
>   The requested resource (/path/page.jsp) is not available.
> 
> Does the forward path have to change?
> 
> -- Robert
Tom Hawtin <usenet@tackline.plus.com> wrote in
 >> Put the JSP under /WEB-INF/.
 >>
 >> Tom Hawtin

Robert Watkins wrote:
 > Hmmm -- must be something I'm missing, because I get a 404 error:
 >
 >   The requested resource (/path/page.jsp) is not available.

It is for the correct value of 'path'.

 > Does the forward path have to change?

It has to include the WEB-INF/ path node.

Either:

  RequestDispatcher dispatcher =
     request.getRequestDispatcher( "/application/WEB-INF/page.jsp" );

or just

  RequestDispatcher dispatcher =
     request.getRequestDispatcher( "WEB-INF/page.jsp" );

I usually use relative paths (always down from current, never up).

BTW, if you had provided an SSCCE instead of paraphrasing as 'path', 
'page.jsp', etc., you'd have had a much clearer question.  Notice how 
hand-waving over 'path' actually obscured the issue?

-- 
Lew

Robert Watkins wrote:>>> Reading the API, it looks as if this should have been the behaviour>>> all along, but that's moot. The question is: How can I prevent direct>>> access to the JSP in another way?Tom Hawtin <usenet@tackline.plus.com> wrote in>> Put the JSP under /WEB-INF/.Robert Watkins wrote:> Hmmm -- must be something I'm missing, because I get a 404 error:> >   The requested resource (/path/page.jsp) is not available.It is for the correct value of 'path'.> Does the forward path have to change?It has to include the WEB-INF/ path node.Either:  RequestDispatcher dispatcher =     request.getRequestDispatcher( "/application/WEB-INF/page.jsp" );or just  RequestDispatcher dispatcher =     request.getRequestDispatcher( "WEB-INF/page.jsp" );I usually use relative paths (always down from current, never up).BTW, if you had provided an SSCCE instead of paraphrasing as 'path', 'page.jsp', etc., you'd have had a much clearer question.  Notice how hand-waving over 'path' actually obscured the issue?-- Lew

Lew <lew@lewscanon.nospam> wrote in news:h5WdnfgGt6mT_OTbnZ2dnUVZ_oavnZ2d@comcast.com:> Tom Hawtin <usenet@tackline.plus.com> wrote in>>> Put the JSP under /WEB-INF/.>>>>>> Tom Hawtin> > Robert Watkins wrote:>> Does the forward path have to change?> > It has to include the WEB-INF/ path node.> Thanks for this final piece of the puzzle. All is working now, with the desired effect.-- Robert