shibboleth-dev - RE: shireURL, providerId, applicationId, and target parameters
Subject: Shibboleth Developers
List archive
- From: "Mark Wilcox" <>
- To: "'Tom Scavo'" <>, "'Howard Gilbert'" <>
- Cc: <>
- Subject: RE: shireURL, providerId, applicationId, and target parameters
- Date: Fri, 5 Nov 2004 12:44:00 -0500
- Importance: Normal
>
> - As you probably know, the web server (Apache) and the app server
> (Tomcat) may be configured so that all requests go through the web
> server to get to the app server. In that case, can't you continue to
> use existing Apache modules and thereby avoid application-level J2EE
> filters?
Yes - this is true. But many Java applications don't run with Apache in
front of them.
So it's all about flexibility (just like why Shib has IIS extensions).
Mark
- shireURL, providerId, applicationId, and target parameters, Howard Gilbert, 11/05/2004
- speaking of the java class, Mark Wilcox, 11/05/2004
- Re: speaking of the java class, Walter Hoehn, 11/05/2004
- RE: speaking of the java class, Mark Wilcox, 11/05/2004
- Re: speaking of the java class, Walter Hoehn, 11/05/2004
- Re: shireURL, providerId, applicationId, and target parameters, Tom Scavo, 11/05/2004
- RE: shireURL, providerId, applicationId, and target parameters, Mark Wilcox, 11/05/2004
- RE: shireURL, providerId, applicationId, and target parameters, Scott Cantor, 11/05/2004
- RE: shireURL, providerId, applicationId, and target parameters, Howard Gilbert, 11/05/2004
- RE: shireURL, providerId, applicationId, and target parameters, Scott Cantor, 11/05/2004
- RE: shireURL, providerId, applicationId, and target parameters, Howard Gilbert, 11/05/2004
- speaking of the java class, Mark Wilcox, 11/05/2004
Archive powered by MHonArc 2.6.16.