FIX: Retain MIME Content-Type Header in HTTP Body (329518)



The information in this article applies to:

  • Microsoft BizTalk Server 2002

This article was previously published under Q329518
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry

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.

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 fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

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.
  1. Run HotfixSetup.exe.
  2. 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.
  3. Restart the BizTalk Messaging service.
NOTE: To turn off this new functionality after you install the hotfix, set the registry value to 0.

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.

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"?>
					


Modification Type:MinorLast Reviewed:10/11/2005
Keywords:kbHotfixServer kbQFE kbBizTalk2002SP1fix kbbug kbfix KB329518 kbAudDeveloper