Re: url-pattern/*.jsp/url-pattern

2004-10-07 Thread Fred Blaise
Well, I am developping a site I would like to block entry to.
However, my .css file is also in this directory, so having a pattern of /* also
blocks access to my css, making the site very ugly to see.

I have tried the following, with no result:
.jsp (no result), jsp (no result), *.jsp (app fails to start)

I haven't tried such thing such as regex.. I haven't seen that anywhere... Woudl
something like /\.jsp$\ work?

Thanks

Fred

Quoting Peter Johnson [EMAIL PROTECTED]:

 url-pattern*.jsp/url-pattern

 But I think that you'll find that this is defined in the core web.xml to
 go to the JSP servlet.

 What are you trying to achieve?


 On Thu, 2004-10-07 at 15:22, Fred Blaise wrote:
  any possible way i can achieve this in my web.xml ? Bc it wont the app
  won't start with this... (tomcat 5.0.28)
 
  url-pattern/*.jsp/url-pattern
 
  thanks
 
  fb.
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



web.xml - security-constraint oddity/problem

2004-10-06 Thread Fred Blaise
Hello

I am running apache 2.0.46 with SSL with tomcat/mod_jk2, white box
linux. I do not have tomcat running SSL on 8443.

So I have this issue with my app... I am securing my app with the
security-constraint tag in web.xml (connected to mysql backend), 

it works perfectly with the url-pattern/clients.jsp/url-pattern.
clients.jsp is a https:// uri, therefore my apache SSL is handling it,
and so is the remaining of the session (?). However, if i throw
url-pattern/index.jsp/url-pattern, which is a http:// uri, then
tomcat tries to connect to port 8443 (instead of 443), where of course
it fails miserably since nothing is running there.

I guess my question is, why is tomcat trying to get to port 8443, when
none of my uri point to https://myhost:8443, but simply to
https://myhost  (which should be handled on port 443 by my apache ssl)?

I don't know if i have been very clear... I always suck at explaining my
pb :P Please ask me if I can clarify

Thanks a lot

Best Regards

Fred


?xml version=1.0 encoding=ISO-8859-1?

!DOCTYPE web-app
   PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
   http://java.sun.com/dtd/web-app_2_3.dtd;

web-app

!-- Beginning of web.xml deployment descriptor --

security-constraint
web-resource-collection
web-resource-nameClient login/web-resource-name
url-pattern/clients.jsp/url-pattern
http-methodGET/http-method
http-methodPOST/http-method
/web-resource-collection

auth-constraint
role-nameclients/role-name
/auth-constraint

user-data-constraint
transport-guaranteeCONFIDENTIAL/transport-guarantee
/user-data-constraint

/security-constraint

login-config

auth-methodFORM/auth-method

form-login-config

form-login-page/login.jsp/form-login-page
form-error-page/loginError.jsp/form-error-page

/form-login-config

/login-config

security-role
role-nameclients/role-name
/security-role

/web-app



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[SOLVED] Re: web.xml - security-constraint oddity/problem

2004-10-06 Thread Fred Blaise
Well, that was an easy fix...
I just changed the redirect port of the Coyote/JK2 AJP 1.3 Connector on
port 8009, to 443 instead of 8443... :)

Fred

On Wed, 2004-10-06 at 22:56 -0500, Fred Blaise wrote:
 Hello
 
 I am running apache 2.0.46 with SSL with tomcat/mod_jk2, white box
 linux. I do not have tomcat running SSL on 8443.
 
 So I have this issue with my app... I am securing my app with the
 security-constraint tag in web.xml (connected to mysql backend), 
 
 it works perfectly with the url-pattern/clients.jsp/url-pattern.
 clients.jsp is a https:// uri, therefore my apache SSL is handling it,
 and so is the remaining of the session (?). However, if i throw
 url-pattern/index.jsp/url-pattern, which is a http:// uri, then
 tomcat tries to connect to port 8443 (instead of 443), where of course
 it fails miserably since nothing is running there.
 
 I guess my question is, why is tomcat trying to get to port 8443, when
 none of my uri point to https://myhost:8443, but simply to
 https://myhost  (which should be handled on port 443 by my apache ssl)?
 
 I don't know if i have been very clear... I always suck at explaining my
 pb :P Please ask me if I can clarify
 
 Thanks a lot
 
 Best Regards
 
 Fred
 
 
 ?xml version=1.0 encoding=ISO-8859-1?
 
 !DOCTYPE web-app
PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
http://java.sun.com/dtd/web-app_2_3.dtd;
 
 web-app
 
 !-- Beginning of web.xml deployment descriptor --
 
 security-constraint
 web-resource-collection
 web-resource-nameClient login/web-resource-name
 url-pattern/clients.jsp/url-pattern
 http-methodGET/http-method
 http-methodPOST/http-method
 /web-resource-collection
 
 auth-constraint
 role-nameclients/role-name
 /auth-constraint
 
 user-data-constraint
 transport-guaranteeCONFIDENTIAL/transport-guarantee
 /user-data-constraint
 
 /security-constraint
 
 login-config
 
 auth-methodFORM/auth-method
 
 form-login-config
 
 form-login-page/login.jsp/form-login-page
 form-error-page/loginError.jsp/form-error-page
 
 /form-login-config
 
 /login-config
 
 security-role
 role-nameclients/role-name
 /security-role
 
 /web-app
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



url-pattern/*.jsp/url-pattern

2004-10-06 Thread Fred Blaise
any possible way i can achieve this in my web.xml ? Bc it wont the app
won't start with this... (tomcat 5.0.28)

url-pattern/*.jsp/url-pattern

thanks

fb.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Home page Administration and Manager links

2004-09-15 Thread Fred Blaise
look under $CATALINA_HOME/server/webapps. Copy manager to the
$CATALINA_HOME/webapps, and change its context path in manager.xml, and
add this directory to your workers2.properties.

That's how i got it to run. Hope it helps.

fb.

On Wed, 2004-09-15 at 12:54 -0500, Pamela Stangl wrote:
 I just un-tarred the binaries for Tomcat 4.1.30 and easily got it to 
 run.   So I'm able to bring up the default Tomcat home page.   But when I 
 select the link for Tomcat Administration or Tomcat Manager under 
 Administration, I get 404 errors.   The Tomcat Administrtaion link is 
 looking for /admin and the Tomcat Manager link is looking for 
 /manager/html  .Neither the /admin or /manager directories exist.
 
 Any help would be appreciated.
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 


signature.asc
Description: This is a digitally signed message part


Re: Home page Administration and Manager links

2004-09-15 Thread Fred Blaise
ahh.. and mine was under tomcat 5.0.28... didn't read careflully enough.
Don't know if it will apply to 4.x.

fb.

On Wed, 2004-09-15 at 12:54 -0500, Pamela Stangl wrote:
 [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Problem rendering JSP 2.0 examples on Tomcat install

2004-09-15 Thread Fred Blaise
it seems like you're passing the wrong argument to the function... 
method: _jspx_meth_mytag_helloWorld_0 signature:
(Ljavax/servlet/jsp/PageContext;)Z) Incompatible argument to function

code?

fb.

On Wed, 2004-09-15 at 17:22 -0600, Luke FERNANDEZ wrote:
 Incompatible argument to function


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



basic FORM-based authentication failing

2004-09-10 Thread Fred Blaise
Hello all

I have been trying to set up FORM based authentication, but it only works
half-way.
When I try to get to the protected resource, it sends me to the login page:
good.
If I authenticate incorrectly, then it sends me to the login error page: good.
If I authenticate _correctly_, it also sends me to the login error page: bad.

I have been reading at jakarta.apache.org, and in JSP  Servlets cookbook, and I
don't know what I am doing wrong. Please find the config files below. My form
uses the j_user_name, j_password and so forth. I have reloaded the app and
restarted tomcat.

Thank you for any help/pointers...

fb.

--tomcat-users.xml (truncated...)
 user username=joedoe password=1joe2 roles=clients/
--end tomcat-users.xml

--web.xml
?xml version=1.0 encoding=ISO-8859-1?

!DOCTYPE web-app
   PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
   http://java.sun.com/dtd/web-app_2_3.dtd;

web-app

!-- Beginning of web.xml deployment descriptor --

security-constraint
web-resource-collection
web-resource-nameClient login/web-resource-name
url-pattern/clients/index.jsp/url-pattern
http-methodGET/http-method
http-methodPOST/http-method
/web-resource-collection

auth-constraint
role-nameclients/role-name
/auth-constraint

user-data-constraint
transport-guaranteeCONFIDENTIAL/transport-guarantee
/user-data-constraint

/security-constraint
login-config

auth-methodFORM/auth-method

form-login-config

form-login-page/login.jsp/form-login-page
form-error-page/loginError.jsp/form-error-page

/form-login-config

/login-config

security-role
role-nameclients/role-name
/security-role

/web-app
--end web.xml

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [SOLVED] basic FORM-based authentication failing

2004-09-10 Thread Fred Blaise
Awful typo... works much better when j_user_name is spelled j_username

Issue resolved.

Thanks.

fb.

Quoting Fred Blaise [EMAIL PROTECTED]:

 Hello all

 I have been trying to set up FORM based authentication, but it only works
 half-way.
 When I try to get to the protected resource, it sends me to the login page:
 good.
 If I authenticate incorrectly, then it sends me to the login error page:
 good.
 If I authenticate _correctly_, it also sends me to the login error page: bad.

 I have been reading at jakarta.apache.org, and in JSP  Servlets cookbook,
 and I
 don't know what I am doing wrong. Please find the config files below. My form
 uses the j_user_name, j_password and so forth. I have reloaded the app and
 restarted tomcat.

 Thank you for any help/pointers...

 fb.

 --tomcat-users.xml (truncated...)
  user username=joedoe password=1joe2 roles=clients/
 --end tomcat-users.xml

 --web.xml
 ?xml version=1.0 encoding=ISO-8859-1?

 !DOCTYPE web-app
PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
http://java.sun.com/dtd/web-app_2_3.dtd;

 web-app

 !-- Beginning of web.xml deployment descriptor --

 security-constraint
 web-resource-collection
 web-resource-nameClient login/web-resource-name
 url-pattern/clients/index.jsp/url-pattern
 http-methodGET/http-method
 http-methodPOST/http-method
 /web-resource-collection

 auth-constraint
 role-nameclients/role-name
 /auth-constraint

 user-data-constraint
 transport-guaranteeCONFIDENTIAL/transport-guarantee
 /user-data-constraint

 /security-constraint
 login-config

 auth-methodFORM/auth-method

 form-login-config

 form-login-page/login.jsp/form-login-page
 form-error-page/loginError.jsp/form-error-page

 /form-login-config

 /login-config

 security-role
 role-nameclients/role-name
 /security-role

 /web-app
 --end web.xml

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



apache ssl or tomcat ssl?

2004-09-09 Thread Fred Blaise
Hello 

Tomcat newbie over here.. I was wondering.. I have my apache server set
up to handle SSL (443) and my tomcat (5.0.28) as well on port 8443.
Is there any reason why I should use the Tomcat SSL, whereas I already
have apache SSL?
Only thing I see at the moment is that some places (like my company)
block outbound ports, so I am able to get to my 443 port, but not 8443.

Thanks.

fb.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]