FIX: Retain MIME Content-Type Header in HTTP Body

View products that this article applies to.

Symptoms

By using reliable messaging and MIME encoding, the HTTP transport moves the MIME Content-Type header to the HTTP Content-Type header. However, you may want to retain the MIME Content-Type header in the HTTP body.

↑ Back to the top

Resolution

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2002. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

815781 How to Obtain the Latest BizTalk Server 2002 Service Pack

Hotfix Information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date          Time    Version      Size      File name
   -----------------------------------------------------------
   15-Oct-2002   22:36   3.0.1542.0   532,752   Sharedcomp.dll

Installation Instructions

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

Run HotfixSetup.exe.
Create a registry value ReliableMIMEoverHTTP of type DWORD under registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTSSvc, and then set its value to 1.
Restart the BizTalk Messaging service.

NOTE: To turn off this new functionality after you install the hotfix, set the registry value to 0.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem was first corrected in Microsoft BizTalk Server 2002 Service Pack 1.

↑ Back to the top

More information

When this hotfix is not installed, the HTTP body starts with the following:

--{AF1EEA12-91EE-44A4-956D-3113674B9FD3}
MIME-Version: 1.0
Content-Type: multipart/signed;
	protocol="application/pkcs7-signature";
	micalg=SHA1;
	boundary="----=_NextPart_000_0009_01C27473.C7ED1660"
Content-Transfer-Encoding: 7bit
Content-Class: 
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

This is a multi-part message in MIME format.

------=_NextPart_000_0009_01C27473.C7ED1660
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-ID: <application/ms-cimessage>

<?xml version="1.0"?>

When the hotfix is installed, the HTTP body starts with the following:

MIME-Version: 1.0
Content-Type: multipart/related;
	boundary="{EA9518FD-3C72-4D86-9F04-61F0E9911BC1}";
	type="multipart/signed"

This is a multi-part message in MIME format.

--{EA9518FD-3C72-4D86-9F04-61F0E9911BC1}
MIME-Version: 1.0
Content-Type: multipart/signed;
	protocol="application/pkcs7-signature";
	micalg=SHA1;
	boundary="----=_NextPart_000_0009_01C27474.49744460"
Content-Transfer-Encoding: 7bit
Content-Class: 
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

This is a multi-part message in MIME format.

------=_NextPart_000_0009_01C27474.49744460
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-ID: <application/ms-cimessage>

<?xml version="1.0"?>

↑ Back to the top