|
Home > Archive > BizTalk Server General > May 2005 > HTTP receive port and encoding
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 receive port and encoding
|
|
| Thiago 2005-05-22, 5:48 pm |
| Hi. I have an html page with a basic form that does an HTTP post to Biztalk's
BTSHTTPReceive.dll on IIS.
It seems that this receiver replaces some characters for their hex value
somehow. I set the receive port with the passthrough pipeline and I also
created a passthrough file send port to save the values to a file. If then I
for example type
<TEST>
on a textbox on the form then when I open up the file created it is replaced
by
%3CTEST%3E
I tried creating a schema with file extensions and a custom pipeline with a
file disassembler referencing that schema and changing the code page to
different values but it still doesn't get the original <TEST>, only %3CTEST%3E
| |
| Tomas Restrepo \(MVP\) 2005-05-24, 2:51 am |
| Thiago,
> Hi. I have an html page with a basic form that does an HTTP post to
> Biztalk's
> BTSHTTPReceive.dll on IIS.
> It seems that this receiver replaces some characters for their hex value
> somehow. I set the receive port with the passthrough pipeline and I also
> created a passthrough file send port to save the values to a file. If then
> I
> for example type
> <TEST>
> on a textbox on the form then when I open up the file created it is
> replaced
> by
> %3CTEST%3E
> I tried creating a schema with file extensions and a custom pipeline with
> a
> file disassembler referencing that schema and changing the code page to
> different values but it still doesn't get the original <TEST>, only
> %3CTEST%3E
This has nothing to do with the character encoding, but rather with the fact
that that's how HTML forms work.. the form is sending the text HTML-encoded.
The easiest way around it would be likely to use a small ASPX page that
decoded the content and submitted it to biztalk through a different
protocol. You could certainly also write a decoding pipeline component that
did the HTML-Decoding (trivial using the framework classes) as well; I'm
sure it might not be hard to do.
--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/
| |
| Thiago 2005-05-25, 5:59 pm |
|
Hi Tomas,
Thank you very much for our response. It has led me to the solution. I
created a custom decoder pipeline component that uses
HttpUtility.UrlDecodeToBytes to decode it.
"Tomas Restrepo (MVP)" wrote:
>
> This has nothing to do with the character encoding, but rather with the fact
> that that's how HTML forms work.. the form is sending the text HTML-encoded.
>
> The easiest way around it would be likely to use a small ASPX page that
> decoded the content and submitted it to biztalk through a different
> protocol. You could certainly also write a decoding pipeline component that
> did the HTML-Decoding (trivial using the framework classes) as well; I'm
> sure it might not be hard to do.
>
>
> --
> Tomas Restrepo
> tomasr@mvps.org
> http://www.winterdom.com/
>
>
>
>
|
|
|
|
|