cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r834704 - in /websites/production/cxf/content: cache/docs.pageCache docs/client-http-transport-including-ssl-support.html
Date Wed, 10 Oct 2012 16:47:31 GMT
Author: buildbot
Date: Wed Oct 10 16:47:31 2012
New Revision: 834704

Log:
Production update by buildbot for cxf

Modified:
    websites/production/cxf/content/cache/docs.pageCache
    websites/production/cxf/content/docs/client-http-transport-including-ssl-support.html

Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/cxf/content/docs/client-http-transport-including-ssl-support.html
==============================================================================
--- websites/production/cxf/content/docs/client-http-transport-including-ssl-support.html
(original)
+++ websites/production/cxf/content/docs/client-http-transport-including-ssl-support.html
Wed Oct 10 16:47:31 2012
@@ -355,6 +355,8 @@ http.setClient(httpClientPolicy);
 
 <p>If your service endpoint uses an SSL WSDL location (i.e., "https://xxx?wsdl"), you
can configure the http conduit to pick up the SSL configuration by using a hardcoded http
conduit name of "{<a shape="rect" href="http://cxf.apache.org/">http://cxf.apache.org/</a>}TransportURIResolver.http-conduit".
 The specific HTTP conduit name or a reg-ex expression can still be used.</p>
 
+<p>Keystores (as identified by the sec:keyStore element above) can be identified via
any one of three ways: via a file, resource, or url attribute.  File locations are either
an absolute path or relative to the working directory, the resource attribute is relative
to the classpath, and URLs must be a valid URL such as "http://..." "file:///...", etc. Only
one attribute of "url", "file", or "resource" is allowed.</p>
+
 <h1><a shape="rect" name="ClientHTTPTransport%28includingSSLsupport%29-AdvancedConfiguration"></a>Advanced
Configuration</h1>
 
 <p>HTTP client endpoints can specify a number of HTTP connection attributes including
whether the endpoint automatically accepts redirect responses, whether the endpoint can use
chunking, whether the endpoint will request a keep-alive, and how the endpoint interacts with
proxies.</p>
@@ -620,8 +622,7 @@ Language tags are regulated by the Inter
 <ul><li>Many proxy servers don't understand it, especially older proxy servers.
  Many proxy servers want the Content-Length up front so they can allocate a buffer to store
the request before passing it onto the real server.</li><li>Some of the older
WebServices stacks also have problems with Chunking.  Specifically, older versions of .NET.</li></ul>
 
 
-<p>If you are getting strange errors (generally not soap faults, but other HTTP type
errors) when trying to interact with a service, try turning off chunking to see if that helps.</p>
-</div>
+<p>If you are getting strange errors (generally not soap faults, but other HTTP type
errors) when trying to interact with a service, try turning off chunking to see if that helps.</p></div>
            </div>
            <!-- Content -->
          </td>



Mime
View raw message