Re: [jetty-dev] Apache Terminated SSL Jetty Proxying w/o custom class

[Chad La Joie <lajoie@xxxxxxxxx>]

Done:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=333340

As I said, if you want me to take a stab at a patch just let me know.

Thanks.

On 12/30/10 9:34 AM, Jesse McConnell wrote:
> Would you create a bugzilla for this issue and we'll kick it
> around...seems reasonable on the surface
>
> cheers,
> jesse
>
> --
> jesse mcconnell
> jesse.mcconnell@xxxxxxxxx
>
>
>
> On Wed, Dec 29, 2010 at 08:29, Chad La Joie<lajoie@xxxxxxxxx>  wrote:
> > According to the docs[1], if one has Apache terminating an SSL connection
> > and proxying requests to Jetty, then you must write a custom extended
> > connector in order to properly deal with this.  That seems like a kind of
> > high bar for something that I would have thought was a decently common
> > setup.  I'd like to propose something to make this scenario a bit simpler.
> >
> > 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.
> >
> > [1] http://docs.codehaus.org/display/JETTY/Configuring+mod_proxy
> > --
> > Chad La Joie
> > http://itumi.biz
> > trusted identities, delivered
> > _______________________________________________
> > jetty-dev mailing list
> > jetty-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/jetty-dev
> _______________________________________________
> jetty-dev mailing list
> jetty-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-dev

--
Chad La Joie
http://itumi.biz
trusted identities, delivered