WCF Behavior Extension to BizTalk WCF-WebHttp Send Port not populating Date Http Header

Question

I have a BizTalk 2013 app (not R2) that needs to send a Json document to an external vendor's RESTful api. The vendor requires three Http headers:

Content-Type: application/json
Date: in ISO8601 UTC format
Authorization: custom auth. using a constructed string that includes the above Date value run through the HMACSHA1 hash

In BizTalk, my outbound (xml) message goes to the Send Port, there is a Custom Pipeline Component that transforms to Json using JSON.Net. So far, so good. To add the headers which are unique per message, I created a WCF Behavior extension that implements IClientInspector and IEndpointBehavior. In BeforeSendRequest(), I get a reference to the HttpRequestMessageProperty for the request.

I can successfully add to the Headers Collection a ContentType header and an Authorization header. I cannot add a Date header - no errors, just no header value when examining with Fiddler.

I read somewhere that Date is a restricted header and for a workaround I could use Reflection to get around it. E.g.

    MethodInfo priMethod = headers.GetType().GetMethod("AddWithoutValidate", BindingFlags.Instance | BindingFlags.NonPublic);
    priMethod.Invoke(headers, new[] { "Date", ISODateTimestamp });

That didn't work either. I'm really stumped with: 1. Why no Date header at all is on my request? 2. If there was one, how I could manipulate it as I need to give that is "restricted"?

I tried two different options: a WCF behavior extension:

public object BeforeSendRequest(ref Message request, System.ServiceModel.IClientChannel channel)
  {
      System.Diagnostics.Debug.Print("Entering BeforeSendRequest()");

      try
      {
          HttpRequestMessageProperty httpRequest = null;

          if (request.Properties.ContainsKey(HttpRequestMessageProperty.Name))
          {
              httpRequest = request.Properties[HttpRequestMessageProperty.Name] as HttpRequestMessageProperty;
          }

          WebHeaderCollection headers = httpRequest.Headers;

          headers.Add(HttpRequestHeader.ContentType, "application/json");
          headers.Add(string.Format("{0}:{1}", "Date", _taxwareHelper.ISODateTimestamp));
          headers.Add("tweDate", _taxwareHelper.ISODateTimestamp);
          headers.Add(HttpRequestHeader.Authorization, _taxwareHelper.AuthorizationString);

and a Custom Pipeline Component in a Send Pipeline

string httpHeaderValue =
    new StringBuilder()
    .Append("Content-Type: application/json")
    .Append("\n")
    //.Append(string.Format("Date:{0}", taxwareHelper.ISODateTimestamp))
    //.Append("\n")
    .Append(string.Format("Date:{0}", "Fri, 10 Jul 2015 08:12:31 GMT"))
    .Append("\n")
    .Append(string.Format("tweDate:{0}", taxwareHelper.ISODateTimestamp))
    .Append("\n")
    .Append(string.Format("Authorization:{0}", taxwareHelper.AuthorizationString))
    .ToString();

pInMsg.Context.Write("HttpHeaders", "http://schemas.microsoft.com/BizTalk/2006/01/Adapters/WCF-properties", httpHeaderValue);

in either case, I can set the Content-Type, the Authorization and test date - tweDate just to test, but I can not set the actual Date header.

Edited the original post to show two different attempts - Custom Pipeline Component and WCF behavior extension. — Frank Hofstaedter, Jul 14 '15 at 11:10

score 0 · Answer 1 · answered Jul 09 '15 at 22:47

0

Yes indeed Date is a special HTTP Header that respresents the date and time at which the message originated but that doesn't prevent you from using it. BUT the date has to be in RFC 822 Format Tue, 15 Nov 1994 08:12:31 GMT
Another thing why do you make it the hard way by coding a behaviour while you could just use HTTPHeaders to add your custom header in your custom pipeline component plus this is so much cleaner

So try to convert your date in the correct format or use HTTPHeaders

http://www.codit.eu/blog/2013/04/30/using-httpheaders-with-wcf-webhttp-adapter-on-biztalk-2013/ http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html

answered Jul 09 '15 at 22:47

mahieddine

540
4
14

Thank you. Because the header values are unique to each message - the Authorization key is unique to each message- I thought I couldn't use the Send Pipeline component because of how it is instantiated. That is why I went with the Wcf behavior extension. I am also aware of the formatting requirement of the date, but the API is demanding the other format. My primary question is why I cannot set that date and see it in Fiddler. – Frank Hofstaedter Jul 09 '15 at 23:09
There are many headers protected by the system like Date, Host, check your log i bet you will see an exception somewhere. As far as know you can't set this header in WCF but you can set it in a custom pipeline (and i don't see why you can do it) you can just promote some values and use them to build your custom values that's it – mahieddine Jul 10 '15 at 00:02
As Frank Hofstaedter points out you can't use the HTTPHeaders context property with headers that are unique per message. Read the last paragraph in the codit blog and also http://stackoverflow.com/questions/24213782/how-to-use-idispatchmessageinspector-in-a-wcf-service. So behavior is the way to go at least. – RobinHu Aug 04 '15 at 13:42

WCF Behavior Extension to BizTalk WCF-WebHttp Send Port not populating Date Http Header

1 Answers1