02-21-07 06:18 AM
If you have a remote site using form authentication, then, usually, there
is an equivalent URL to achieve the form authentication. It is usually in
the form of something like
http://remotesite/login.aspx?userna...erparam=xxx....
You can directly put that into HTTP Send port URL. If you directly use
that, then it is better remote host use https. Otherwise, the username
password is set in clear text
If you don't want to show your URL in http send port configuration, you can
use Dynamic Send Port. You can use an orchestration message construction
shape before deliver message to dynamic http send port. Using that, you
can specify URL in the your message's OutboundTransportLocation property.
And you can set all kinds of HTTP request header using the properties
attach to http request, you code will be like:
YourMessage(Http.HTTP_PROPERTYNAME)=your value;
This will give you almost total control of your HTTP send request.
--------------------[vbcol=seagreen]
<BizTalkDeveloper@discussions.microsoft.com>[vbcol=seagreen]
HTTP[vbcol=seagreen]
one[vbcol=seagreen]
[ Post a follow-up to this message ]
|