camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: Intercepting https endpoints with proxy config not working
Date Sat, 02 Mar 2013 17:52:59 GMT
Hi

I suggest to use wildcards when intercepting such long uris.
http://camel.apache.org/intercept

On Thu, Feb 14, 2013 at 9:31 AM, ddewaele <ddewaele@gmail.com> wrote:
> Hi,
>
> I'm trying to intercept the following https endpoint using the
> camel:interceptSendToEndpoint component :
>
> <camel:to
> uri="https4://endpoint?sslContextParametersRef=sslContextParameters&amp;throwExceptionOnFailure=false&amp;proxyAuthScheme={{app.proxy.authScheme}}&amp;proxyAuthHost={{app.proxy.authHost}}&amp;proxyAuthPort={{app.proxy.authPort}}&amp;proxyAuthUsername={{app.proxy.authUsername}}&amp;proxyAuthDomain={{app.proxy.authDomain}}&amp;proxyAuthPassword={{app.proxy.authPassword}}&amp;proxyAuthNtHost={{app.proxy.authNtHost}}"
> />
>
> (the app.proxy things are being fetched from a properties file and they work
> fine when not intercepted).
>
> Unfortunately, intercepting this endpoint doesn't work. If I remove the
> proxy parameters from the endpoint and change it to this :
>
> <camel:to
> uri="https4://endpoint?sslContextParametersRef=sslContextParameters&amp;throwExceptionOnFailure=false"
> />
>
> I am able to intercept it just fine using the camel:interceptSendToEndpoint.
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Intercepting-https-endpoints-with-proxy-config-not-working-tp5727571.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Mime
View raw message