INT-2035 Support Simple Cookie Handling
Initial commit - TODO: namspace. Saves off Set-Cookie header in http_transferredCookie MessageHeader. Transferred cookies are converted to Cookie: headers on subsequent outbound messages, thus handling 3 or more interactions. INT-2035 Namespace, Docs Change boolean name; add namspace and documentation. INT-2035 Docs Added docs for cookie handling. INT-2035 Polishing Simplify implementation to just transfer Set-Cookie to Cookie in the inbound side. INT-2035 XSD Docs Updated to reflect new implementation.
This commit is contained in:
committed by
Mark Fisher
parent
497d07bdad
commit
a61b3617f3
@@ -100,6 +100,20 @@ By default the HTTP request will be generated using an instance of <classname>Si
|
||||
In the case of the Outbound Gateway, the reply message produced by the gateway will contain all Message Headers present in the request message.
|
||||
</note>
|
||||
</para>
|
||||
<para><emphasis>Cookies</emphasis></para>
|
||||
<para>
|
||||
Basic cookie support is provided by the <emphasis>transfer-cookies</emphasis> attribute on the outbound gateway. When
|
||||
set to true (default is false), a <emphasis>Set-Cookie</emphasis> header received from the server in a response will be
|
||||
converted to <emphasis>Cookie</emphasis> in the reply message. This header will then be used
|
||||
on subsequent sends. This enables simple stateful interactions, such as...
|
||||
</para>
|
||||
<para>
|
||||
<emphasis>...->logonGateway->...->doWorkGateway->...->logoffGateway->...</emphasis>
|
||||
</para>
|
||||
<para>
|
||||
If <emphasis>transfer-cookies</emphasis> is false, any <emphasis>Set-Cookie</emphasis> header received will
|
||||
remain as <emphasis>Set-Cookie</emphasis> in the reply message, and will be dropped on subsequent sends.
|
||||
</para>
|
||||
</section>
|
||||
|
||||
<section id="http-namespace">
|
||||
|
||||
Reference in New Issue
Block a user