camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r916510 - in /websites/production/camel/content: cache/main.pageCache netty-http.html
Date Thu, 17 Jul 2014 12:18:25 GMT
Author: buildbot
Date: Thu Jul 17 12:18:25 2014
New Revision: 916510

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/netty-http.html

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

Modified: websites/production/camel/content/netty-http.html
==============================================================================
--- websites/production/camel/content/netty-http.html (original)
+++ websites/production/camel/content/netty-http.html Thu Jul 17 12:18:25 2014
@@ -115,7 +115,7 @@
                     <p class="title">Query parameters vs endpoint options</p>
                             <span class="aui-icon icon-hint">Icon</span>
                 <div class="message-content">
-                            <p>You may be wondering how Camel recognizes URI query
parameters and endpoint options. For example you might create endpoint URI as follows - <code>netty-http:http//example.com?myParam=myValue&amp;compression=true</code>
. In this example <code>myParam</code> is the HTTP parameter, while <code>compression</code>
is the Camel endpoint option. The strategy used by Camel in such situations is to resolve
available endpoint options and remove them from the URI. It means that for the discussed example,
the HTTP request sent by Netty HTTP producer to the endpoint will look as follows -&#160;<code>http//example.com?myParam=myValue</code>
, because <code>compression</code> endpoint option will be resolved and removed
from the target URL.</p>
+                            <p>You may be wondering how Camel recognizes URI query
parameters and endpoint options. For example you might create endpoint URI as follows - <code>netty-http:http//example.com?myParam=myValue&amp;compression=true</code>
. In this example <code>myParam</code> is the HTTP parameter, while <code>compression</code>
is the Camel endpoint option. The strategy used by Camel in such situations is to resolve
available endpoint options and remove them from the URI. It means that for the discussed example,
the HTTP request sent by Netty HTTP producer to the endpoint will look as follows -&#160;<code>http//example.com?myParam=myValue</code>
, because <code>compression</code> endpoint option will be resolved and removed
from the target URL.</p><p>Keep also in mind that you cannot specify endpoint
options using dynamic headers (like <code>CamelHttpQuery</code>). Endpoint options
can be specified only at the endpoint URI definition level (like <code>to</code>
or <code
 >from</code> DSL elements).</p>
                     </div>
     </div>
 <h3 id="NettyHTTP-HTTPOptions">HTTP Options</h3>    <div class="aui-message
hint shadowed information-macro">



Mime
View raw message