|[jetty-dev] Apache Terminated SSL Jetty Proxying w/o custom class|
First, add a couple fields, with corresponding getter/setters, to the connector that would track the scheme and "secure"ness of the request. Then have the default customize(Endpoint, Request) method check if those values are null. If they are, do what is done today. If not, set the corresponding properties on the request as appropriate.
This would be a backwards compatible addition but would also make dealing with the Apache-terminated SSL case much simpler to deal with. If this seems reasonable I'll write up a patch for it.
 http://docs.codehaus.org/display/JETTY/Configuring+mod_proxy -- Chad La Joie http://itumi.biz trusted identities, delivered
Back to the top