cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <dk...@apache.org>
Subject Re: Are properties not resolved in http:conduit
Date Mon, 09 Mar 2009 18:10:51 GMT

It looks like you set the:
http-conf:authorization 
stuff (through config or through code), but didn't set the 
http-conf:proxyAuthorization
which would provide the basic auth stuff for communicating with the proxy 
server.   

Dan


On Mon March 9 2009 9:56:18 am Olivier Billard wrote:
> From TCPmon :
>
> With an HTTP URL endpoint :
> POST http://endpoint-server/endpoint-url Content-Type: text/xml;
> charset=UTF-8
> Authorization: Basic <snip/>
> SOAPAction: ""
> Accept: *
> Connection: Keep-Alive
> Cache-Control: no-cache
> Pragma: no-cache
> User-Agent: Java/1.6.0_07
> Host: proxy-server:proxy-port
> Proxy-Connection: keep-alive
> Content-Length: 834
>
>
> With an HTTPS URL endpoint :
> CONNECT endpoint-server:443 HTTP/1.1
> User-Agent: Java/1.6.0_07
> Host: proxy-server:proxy-port
> Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
>
> And in this case, the CXF client does not reply to the HTTP Basic
> authentication challenge.
> Is there a particular configuration to set, different from [1] (cxf-2.1.4)
> ?
>
>
> [Edit] and with the call to Authenticator.setDefault(...) added, the
> challenge is replied correctly :
>
> CONNECT endpoint-server:443 HTTP/1.1
> User-Agent: Java/1.6.0_07
> Host: proxy-server:proxy-port
> Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
> Proxy-authorization: Basic <snip />
>
> [/Edit]
>
> Thank you !
>
> [1] http://cwiki.apache.org/CXF20DOC/client-http-transport.html
> --
> Olivier Billard
>
> Olivier Billard wrote:
> > Hi all,
> >
> > I still have a problem against corporate proxy authentication.
> > To help solve this, it works against standard HTTP connection, but not if
> > the endpoint is reached through HTTPS. I have to add the following code
> > (not production code for the moment) in my client to configure proxy
> > authorization. This only thing that varies in configuration is endpoint
> > URL.
> >
> > <code>
> >         (...)
> >         Authenticator.setDefault(new Authenticator() {
> >             @Override
> >             protected PasswordAuthentication getPasswordAuthentication()
> > { return new PasswordAuthentication("username",
> > "password".toCharArray());
> >             }
> >         });
> >         (...)
> > </code>
> >
> > --
> > Olivier Billard
> >
> > dkulp wrote:
> >> Any chance you could produce a small sample for this?   I just tried and
> >> it
> >> seemed to work fine.
> >>
> >> Dan
> >>
> >> On Tuesday 27 January 2009 2:16:30 pm jmdev wrote:
> >>> Just to add to this thread, I am having trouble with Spring property
> >>> resolution in http:client and http:proxyAuthorization as well.
> >>>
> >>> http:tlsClientParameters works fine however.
> >>>
> >>> jmdev wrote:
> >>> > It appears to work for the conduit now.  Thanks!  The "address"
> >>>
> >>> property
> >>>
> >>> > of jaxws:client does not appear to work however.  Does that require
a
> >>> > similar fix?
> >>> >
> >>> > dkulp wrote:
> >>> >> On Tuesday 09 December 2008 11:23:35 am Daniel Kulp wrote:
> >>> >>> On Tuesday 09 December 2008 8:44:46 am jmdev wrote:
> >>> >>> > I am using 2.1.4 SNAPSHOT and am still not able to get
this
> >>>
> >>> working.
> >>>
> >>> >>> Is
> >>> >>>
> >>> >>> > there anything special one needs to do to get the
> >>> >>> > PropertyPlaceholderConfigurer to be recognized?  Is there
an
> >>>
> >>> example
> >>>
> >>> >>> or
> >>> >>>
> >>> >>> > test case that you could refer me to if available.
> >>> >>>
> >>> >>> Arg....    I just checked the code and the TLSClientParameters
are
> >>> >>> treated
> >>> >>> differently in the code for some reason and thus stuff in there
> >>>
> >>> doesn't
> >>>
> >>> >>> get
> >>> >>> properly processed.   I'll see what can be done here.   Shouldn't
> >>> >>> be too hard.    (famous last words)
> >>> >>
> >>> >> Just committed some changes to trunk.   Any chance you could
> >>> >> checkout trunk,
> >>> >> build it and check to make sure it works?   I may get a chance
to do
> >>> >> another
> >>> >> snapshot tomorrow if not.
> >>> >>
> >>> >> --
> >>> >> Daniel Kulp
> >>> >> dkulp@apache.org
> >>> >> http://dankulp.com/blog
> >>
> >> --
> >> Daniel Kulp
> >> dkulp@apache.org
> >> http://dankulp.com/blog

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

Mime
View raw message