camel-commits mailing list archives

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

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 Jun 12 12:17:50 2014
@@ -111,7 +111,14 @@
 </div></div><h3 id="NettyHTTP-URIformat">URI format</h3><p>The
URI scheme for a netty component is as follows</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[netty-http:http://localhost:8080[?options]
 ]]></script>
-</div></div><p>You can append query options to the URI in the following
format, <code>?option=value&amp;option=value&amp;...</code></p><h3
id="NettyHTTP-HTTPOptions">HTTP Options</h3>    <div class="aui-message hint shadowed
information-macro">
+</div></div><p>You can append query options to the URI in the following
format, <code>?option=value&amp;option=value&amp;...</code></p>
   <div class="aui-message hint shadowed information-macro">
+                    <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>
+                    </div>
+    </div>
+<h3 id="NettyHTTP-HTTPOptions">HTTP Options</h3>    <div class="aui-message
hint shadowed information-macro">
                     <p class="title">A lot more options</p>
                             <span class="aui-icon icon-hint">Icon</span>
                 <div class="message-content">



Mime
View raw message