Thank you for you answer, Dan. The problem is trickier, as the configuration works with HTTP (I can pass through the corporate proxy), and not HTTPs.
With HTTP, Proxy-Authorization and Authorization request headers are already set in the first POST request (see my previous message). But with HTTPS, no such header is set, even after the Proxy Auth challenge sent by the corporate proxy. The path is the following : [Client] -> [Corporate proxy, Auth required] -> [Web service server, Basic Auth] I did set both http-conf:authorization and http-conf:proxyAuthorization, but I might have set it in a wrong way, you could be right about it. Here is the conduit configuration: <http:conduit name="*.http-conduit"> <http:tlsClientParameters disableCNCheck="true" secureSocketProtocol="SSL"> <sec:trustManagers> <sec:keyStore type="JKS" password="pass" resource="truststore.jks" /> </sec:trustManagers> </http:tlsClientParameters> <!-- Corporate proxy configuration --> <http:client AllowChunking="false" ProxyServer="${proxy.host}" ProxyServerPort="8080" /> <!-- Application Basic Auth --> <http:authorization> <sec:UserName>${application.username}</sec:UserName> <sec:Password>${application.password}</sec:Password> </http:authorization> <!-- Proxy Auth --> <http:proxyAuthorization> <sec:UserName>${proxy.username}</sec:UserName> <sec:Password>${proxy.password}</sec:Password> </http:proxyAuthorization> </http:conduit> dkulp wrote: > > > 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 > -- > Daniel Kulp > dk...@apache.org > http://www.dankulp.com/blog > > -- View this message in context: http://www.nabble.com/Are-properties-not-resolved-in-http%3Aconduit-tp20444369p22430044.html Sent from the cxf-user mailing list archive at Nabble.com.