On Mon, Jul 18, 2011 at 2:23 AM, Don Doffe <forrestl...@gmail.com> wrote: > Hi Claus, > > sorry I could not check the fix on the weekend. I have shut down my work PC > by mistake (instead of rebooting it) over the VPN. > > I have run the scenario Camel -- HTTP --> proxy -- HTTPS --> destination. > Seem to work. > > Will this fix be back ported to 2.8.0 at some stage or will it be available > from 2.9.0 only?
The fix will be part of Camel 2.8. We will cut a new release this week. Then there will be a new RC of 2.8 which you can give a test and post your comments/findings in the VOTE thread. So keep an eye on the @dev mailing list. > > > > > On the side note. I was not able to test > > Camel -- HTTPS --> proxy -- HTTPS --> destination. > > Out proxy does not support HTTPS connections to it as it seems. > The only thing I wanted to double check which host verifier will be used for > proxy if HTTPS scheme is being used? > My understanding that it should be the same as for the main connection, i.e. > the one defined as the parameter. > I am almost certain the source code uses the host verifier configured on the endpoint. > Could you please confirm if my understanding is correct? > > > Thank you. > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/CAMEL-4176-fix-tp4597697p4597697.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
