You can place your jsps in the WEB-INF directory. They will be
accessible for the Struts request dispatcher then, but not by direct
user call.
M.Liang Liu schrieb:
I just would like to block users to get to the login.jsp through the
url:http://somedomain.com/login.jsp.
Instead,users can login
-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/How-to-keep-users-from-accessing--to-*.jsp-strightforword--tf4077945.html#a11592535
Sent from the Struts - User mailing list archive at Nabble.com
Yes. I use this for years now , works perfect
M.Liang Liu schrieb:
Sounds good.
My friend said that spring mvc prefer this style.
How can I deal with the *result* mapping then ?
thanks.
Rene Gielen wrote:
You can place your jsps in the WEB-INF directory. They will be
accessible for
://somedomain.com/login.action.
And what I would like to do is block the direct *.jsp access.
Any comment would be greatly appreciated.
--
View this message in context:
http://www.nabble.com/How-to-keep-users-from-accessing--to-*.jsp-strightforword--tf4077945.html#a11590867
Sent from the Struts - User
@struts.apache.org
Subject: How to keep users from accessing to *.jsp strightforword?
I just would like to block users to get to the login.jsp through the
url:http://somedomain.com/login.jsp.
Instead,users can login with the url :http://somedomain.com/login.action---
actually the login.jsp page.
With the help
@struts.apache.org
Subject: How to keep users from accessing to *.jsp strightforword?
I just would like to block users to get to the login.jsp through the
url:http://somedomain.com/login.jsp.
Instead,users can login with the url :http://somedomain.com/login.action---
actually the login.jsp page
6 matches
Mail list logo
