Select the product you need help with
FIX: The BizTalk Server 2004 HTTP Adapter does not support setting HTTP headers on response from the serverArticle ID: 837441 - View products that this article applies to. On This PageSYMPTOMSThe Microsoft BizTalk Server 2004 HTTP Adapter does not currently support the setting of HTTP headers on the response from a HTTP receive request from an Orchestration. RESOLUTIONService pack informationTo resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base:888751
(http://support.microsoft.com/kb/888751/
)
How to obtain the latest BizTalk Server 2004 service pack
Hotfix informationThe English version of this hotfix 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 ------------------------------------------------------------------------------------ 10-Mar-2004 22:24 3.0.5255.0 144,384 Btshttpreceive.dll 10-Mar-2004 21:50 3.0.5255.0 720,896 Microsoft.biztalk.globalpropertyschemas.dll 10-Mar-2004 22:24 3.0.5255.0 65,536 Microsoft.biztalk.httptransport.dll STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was corrected in BizTalk Server 2004 Service Pack 1.
MORE INFORMATIONThe new context property is the UserHttpHeaders property. When you specify a header value in the UserHttpHeaders property, it will be added to the outbound request HTTP response. The value must have the following format: Header1: value\r\nHeader2: value\r\n Note Put a colon (":") and a SPACE character (" ") between the header and the value.PropertiesArticle ID: 837441 - Last Review: August 17, 2006 - Revision: 3.1
|


Back to the top








