We have a situation where certain appservers are behind a webserver proxy, but also available to internal users directly. This means that the SSLEXT plugin must sometime rewrite the URLs based on ports 80 and 443, and sometimes between 7001 and 7002. This will remain constant throughout a particular user's session.
I've taken a brief look at the SSLEXT code, and it doesn't look very extensible (without modifications). The SecureRequestUtils.computeURL method is static, and the SecurePlugInInterface to which it delegates the selection of port numbers is shared throughout the app (in ServletContext) with no access to the incoming request. Has anyone else ever slayed this particular dragon? I'd hate to reinvent the wheel unnecessarily. - George -- George Dinwiddie 410-884-6473 [EMAIL PROTECTED] [EMAIL PROTECTED] "There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies." -- C. A. R. Hoare --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
