Return-Path: Delivered-To: apmail-jakarta-struts-user-archive@jakarta.apache.org Received: (qmail 18743 invoked by uid 500); 1 Oct 2001 11:52:03 -0000 Mailing-List: contact struts-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: struts-user@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list struts-user@jakarta.apache.org Received: (qmail 18736 invoked from network); 1 Oct 2001 11:52:03 -0000 Received: from c000-h001.c000.snv.cp.net (HELO c000.snv.cp.net) (209.228.32.65) by daedalus.apache.org with SMTP; 1 Oct 2001 11:52:03 -0000 Received: (cpmta 4040 invoked from network); 1 Oct 2001 04:52:02 -0700 Received: from 146-115-72-145.c3-0.brl-ubr1.sbo-brl.ma.cable.rcn.com (HELO javelinsoftware.com) (146.115.72.145) by smtp.javelinsoftware.com (209.228.32.65) with SMTP; 1 Oct 2001 04:52:02 -0700 X-Sent: 1 Oct 2001 11:52:02 GMT Message-ID: <3BB85940.F8D9B194@javelinsoftware.com> Date: Mon, 01 Oct 2001 07:53:36 -0400 From: Steven Valin X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: struts-user@jakarta.apache.org Subject: Re: security question References: <45A6414F7738D31195DD0008C75DB92904CA2C2A@ffz00zai.wwz1me.mail.dresdner.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Interesting. A reply from their tech support indicates that WebLogic 6 still does not permit this, as do my own tests. "Khorramrouz, Turaj" wrote: > Hi Jonathan, > you don't have the problem with "RequestDispatching to JSPs underneath > WEB-INF" in weblogic 5.1 with sp 10 any more. > > regards, > > Turaj > > > -----Original Message----- > From: Jonathan M Crater [mailto:jonathan_m_crater@fanniemae.com] > Sent: Montag, 24. September 2001 17:49 > To: struts-user@jakarta.apache.org > Subject: security question > > i'm using weblogic 5.1, which does not allow RequestDispatching to JSPs > underneath WEB-INF. so i'm stuck keeping my JSPs outside WEB-INF. as a > result, > i have to secure requests to both JSPs and actions. securing the actions is > just a matter of sub-classing ActionServlet and providing logic to check for > certain secured paths. the problem is i don't want to repeat the logic in > the JSPs--either through a tag library or otherwise. does anyone have any > suggestions as to how best to prevent a situation where a user requests a > JSP page directly when it should have gone through the sub-classed > ActionServlet? i was thinking of just setting a request parameter for each > request as it passes through the ActionServlet. that way, in the JSP i can > just test for that value to determine whether the request went through the > proper channel. if not, i can redirect to an error page. > > thoughts? suggestions? -- Steven Valin steven.valin@javelinsoftware.com