|
Home > Archive > BizTalk Server Administration > June 2005 > HTTP adapter lowercases Content type - bug ?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
HTTP adapter lowercases Content type - bug ?
|
|
| eXavier 2005-03-21, 7:47 am |
| Hi all,
I needed to use Biztalk HTTP adapter (solicit response two way port) to send
data over HTTPS to specific customer server. Customer has defined content of
HTTP request as multipart, so I constructed the data message according to
contract and set up Send port HTTP Transport Properties. In General tab I
set Content Type field to value "multipart/mixed; boundary=BOUNDARY". After
some time of failing tests I intercepted data sent over HTTP and I figured
out that biztalk lowercases value of Content Type, so "BOUNDARY" became
"boundary". This was the reason while customer server failed to process the
request. To solve the problem I changed case of boundary string in
constructed message and request was processed successfully.
Is this a bug in biztalk adapter? I haven't noticed about lowercasing of
port configuration in documentation. I point out this behaviour to avoid
other developers loosing their time with this issue.
eXavier
| |
| Cristian Ciccioli 2005-05-04, 5:54 pm |
| Hi Xavier. I'm trying to do the same thing.
I'm not setting the boundaries explicitly, and seems that MIME encoder set
them by itself. So the MIME file generated is right. But the receiver
application doesn't recognize the attachments. I'm opening the request data
received by the destination application using outlook express and the MIME
file is right, because it contains all the attachments, but the ASP.NET
application that receive them shows me Request.Files.Count equal to zero.
Did you do it in a different manner?
"eXavier" wrote:
> Hi all,
> I needed to use Biztalk HTTP adapter (solicit response two way port) to send
> data over HTTPS to specific customer server. Customer has defined content of
> HTTP request as multipart, so I constructed the data message according to
> contract and set up Send port HTTP Transport Properties. In General tab I
> set Content Type field to value "multipart/mixed; boundary=BOUNDARY". After
> some time of failing tests I intercepted data sent over HTTP and I figured
> out that biztalk lowercases value of Content Type, so "BOUNDARY" became
> "boundary". This was the reason while customer server failed to process the
> request. To solve the problem I changed case of boundary string in
> constructed message and request was processed successfully.
>
> Is this a bug in biztalk adapter? I haven't noticed about lowercasing of
> port configuration in documentation. I point out this behaviour to avoid
> other developers loosing their time with this issue.
>
> eXavier
>
>
>
>
| |
| karahan@gmail.com 2005-06-02, 5:51 pm |
| Hi eXavier,
This is a known HTTP adapter bug in BizTalk 2004 SP1.
"
The HTTP adapter incorrectly converts the whole ContentType header to
lowercase characters in BizTalk Server 2004 Service Pack 1 (SP1)
"
You can obtain a hotfix for it by calling PSS (Microsoft Product
Support Services).
Here is the link for the KB, and the PSS phone numbers.
http://support.microsoft.com/defaul...kb;en-us;895107
| |
| Dinesh 2005-06-24, 5:54 pm |
| I am looking for asp.net client which can receive xml file sent by Biztalk
http sent adapter. Pls send to me if any one has the same.
Thanks,
"karahan@gmail.com" wrote:
> Hi eXavier,
>
> This is a known HTTP adapter bug in BizTalk 2004 SP1.
>
> "
> The HTTP adapter incorrectly converts the whole ContentType header to
> lowercase characters in BizTalk Server 2004 Service Pack 1 (SP1)
> "
>
> You can obtain a hotfix for it by calling PSS (Microsoft Product
> Support Services).
>
> Here is the link for the KB, and the PSS phone numbers.
>
> http://support.microsoft.com/defaul...kb;en-us;895107
>
>
|
|
|
|
|