Created a HTTP Send Port and configured the authentication, URL, and
content-type property and fired off the request. Their application did not
receive the post as per to their requirements. After going through a lot of
red tape, finally was able to get my hands on what a sample post might look
like. Here it is:
POST /dev/Receive/... HTTP/1.1
Pragma: no-cache
Content-Length: 39798
Content-Type: multipart/form-data;
boundary=----------------------------b1be518f1a69
Accept: */*
Expect: 100-continue
Host: localhost
User-Agent: curl/7.12.2 (i386-pc-win32) libcurl/7.12.2 OpenSSL/0.9.7c
zlib/1.2.1
------------------------------b1be518f1a69
Content-Disposition: form-data; name="filename"; filename="catalogue.xml"
Content-Type: application/octet-stream
<?xml version="1.0" encoding="iso-8859-1"?>
<Catalog>
<data>blaah</data>
</Catalog>
------------------------------b1be518f1a69--
It looks like some type of mime encapsulation with all this boundary info.
I have not been able to replicate this type of a post from BizTalk using the
HTTP Send port and in combination with the MIME parser in the send pipeline.
Bottom line is: IS THERE a way to get this type of xml over http using
BizTalk 2004?.
Thank in advance for any help!
Kind regards,
aman
Someone may have already built one that they may like to share - he said
hopefully
It is on my to do list, along with a HTTP/HTML Form adapter
Greg
"aman" <am...@discussions.microsoft.com> wrote in message
news:C5A50533-1C82-4A5B...@microsoft.com...
Greg, thanks a bunch for your input.