Building mod_webapp from sources with Apache 2

2002-04-13 Thread Fredrik Westermarck

Hi!

I have been browsing around all of the Jakarta-site (including the CVS) 
for instructions on how to build mod_webapp 
(jakarta-tomcat-connectors-4.0.2-01) from source with Apache 2.0.x.

All of the documentation I have found so far only covers how to build 
mod_webapp with Apache 1.3.x.

Are there any instructions on how to build mod_webapp with Apache 2.0.x?

Regards,
Fredrik Westermarck


--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]




Re: reading content in WEB-INF

2002-02-19 Thread Fredrik Westermarck

Max Z. wrote:
 I am storing a file in the WEB-INF directory and I need to access it with a
 servlet, how would I get to it?
 

Use:

InputStream is =
  getServletContext().getResourceAsStream(/WEB-INF/your.file);


--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]




Re: JNDIRealm

2002-02-01 Thread Fredrik Westermarck

On Sat, 2 Feb 2002, John Holman wrote:

 Have the proposal been approved by the Tomcat developers, and are there
 any people working on this issue?
 Similar proposals are in the draft functional specification for the JNDI
 realm, and I submitted a patch to the tomcat-dev list earlier today
 that implements the required functionality.

Great!

 You are more than welcome to try it, if you get the chance.

Yes, I'll try it out as soon as possible. I have to setup my
environment so that I can build tomcat from sources first.

-- 
---
Fredrik WestermarckSystemutvecklare/IT-avdelningen
Mälardalens högskola   Tel   +46-21-103162
Box 883Fax   +46-21-101636
721 23 VästeråsEpost [EMAIL PROTECTED]
---


--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]




Re: JNDIRealm

2002-01-29 Thread Fredrik Westermarck

John Holman wrote:
 
 JNDIRealm works by retrieving the password from the directory server and
 comparing it explicitly with the value given by
 the user. Unfortunately AFAIK this mode of operation will not work with
 eDirectory.

Reading the Realm HOWTO again made me realize that... Why would anyone
want the Realm to get the password from the server instead of doing a
simple LDAP bind?

 There have been proposals (e.g. from me) to enhance JNDIRealm to allow it
 to authenticate the user by binding to the directory server, in the same
 way as auth_ldap. This should work with eDirectory, but isn't available yet.

Have the proposal been approved by the Tomcat developers, and are there
any people working on this issue?

-- 
Fredrik Westermarck

--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]




JNDIRealm

2002-01-28 Thread Fredrik Westermarck

Hi!

We are going to upgrade to Tomcat and are investigating how to implement
user authentication. Currently we are using the authentication that is
offered in Apache with auth_ldap.

Since Tomcat offers an authentication mechanism (Realms) we would like
to use that functionality. However since we are using Novell NDS
(eDriectory) to store our users and have several NDS servers, we would
like to have Tomcat to authenticate a user against one or more of the
NDS servers. Is this possible?

As far as I can see the JNDIRealm can only handle a single server to
authenticate users against.

-- 
Fredrik Westermarck

--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]




Upgrading from JServ/Apache to Tomcat/Apache

2002-01-15 Thread Fredrik Westermarck

Hi!

We have been using JServ/Apache for a long long time. Since JServ is not
supported anymore we need to upgrade to Tomcat/Apache to be able to use
JSPs.

We want to keep our existing URLs (/servlet/) and have the possibility
to have JSPs in the htdocs folder. We want the following mappings:

/servlet/ - Tomcat
/*.jsp- Tomcat
All of the rest should be served by Apache as defined in httpd.conf.

Question: Which combination of Tomcat/Apache module can be used to
achieve this?
Tomcat 3.2/3.3/4.0? mod_jk/mod_webapp?

-- 
---
Fredrik Westermarck
---

--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]




Re: Wrap an HttpServletRequest

2001-11-14 Thread Fredrik Westermarck

Martin van den Bemt wrote:
 
 Pas the request object to that servlet eg
 BlahServlet servlet = new BlahServlet();
 servlet.execute(req, resp);

Why not get a RequestDispatcher and forward (or include) to the other
servlet?

..
  RequestDispatcher rd = request.getRequestDispatcher(pathToServlet);
  rd.forward(request, response); // or rd.include(request, response)
..

Use the setAttribute()-method in the servlet that handles the original
request to add the extra parameters. Then use getAttribute() in the
servlet that you forwarded or included to read the extra parameters.

-- 
Fredrik Westermarck

--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]




Re: Logout with basic autorization

2001-11-14 Thread Fredrik Westermarck

kevin ritter wrote:
 
 Can anyone one verify if this is really the case, that is, to logout with
 BASIC authentication you have to close the browser window? This seems to be
 a little goofy. Are there any work arounds?

The troubles of revoking user credentials when using HTTP-authentication
is documented in the HTTP/1.1 specification (probably 1.0) under
http://www.w3.org/Protocols/rfc2616/rfc2616-sec15.html#sec15.6.

The only reliable way of logging out when you have been authenticated
(if using HTTP-authentication) is to close _all_ of your browser
windows.

-- 
Fredrik Westermarck

--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]