none
Wcf - Mtom: How to format boundary value within MIME header? RRS feed

  • Question

  • I'm currently stuck with a problem related to 'boundary' value within the MIME header. We have a wcf service with custom binding to support mtom. Here is a portion of sample MIME header that we are getting out of our service:

    content-type: multipart/related; type="application/xop+xml";start="<http://tempuri.org/0>";boundary="uuid:f45e6739-e796-41c7-bc96-6dd977a185f6+id=2";start-info="application/soap+xml"

    We are using NIST message validator to validate the message and the validator is not liking the 'boundary' value for some reason and the validation fails. In the above sample boundary value, if I just take out '=' sign and make it look like boundary="uuid:f45e6739-e796-41c7-bc96-6dd977a185f6+id2", the validation passes. So can you please guide me in getting rid of this '=' sign from the boundary value?

    Thanks.


    • Edited by sharu80 Wednesday, June 12, 2013 9:29 PM typo
    Wednesday, June 12, 2013 9:28 PM

Answers

  • Hi, I do not find a workaround after research, it seems something like below is a correct one.

    Content-Type: Multipart/Related; type="application/xop+xml";start-info="text/xml";boundary="uuid:0ca0e16e-feb1-426c-97d8-c4508ada5e82+id=1"
     
    

    http://msdn.microsoft.com/en-us/library/aa738574.aspx?ppud=4
    • Proposed as answer by Nico_He Wednesday, June 19, 2013 8:25 AM
    • Marked as answer by Haixia_XieModerator Friday, June 21, 2013 6:31 AM
    Friday, June 14, 2013 6:27 AM
  • Thanks a lot for looking into this, it did help us in confirming the behavior. Even we found out that the boundary format with 'equal to' sign is a valid format by going through some of the microsoft blogs. It might be something to do with the NIST validatory treating 'equal to' sign in a different manner. Will try to get in touch with someone from NIST team on this.

    sharath

    Wednesday, June 19, 2013 2:02 PM

All replies

  • Hi, I do not find a workaround after research, it seems something like below is a correct one.

    Content-Type: Multipart/Related; type="application/xop+xml";start-info="text/xml";boundary="uuid:0ca0e16e-feb1-426c-97d8-c4508ada5e82+id=1"
     
    

    http://msdn.microsoft.com/en-us/library/aa738574.aspx?ppud=4
    • Proposed as answer by Nico_He Wednesday, June 19, 2013 8:25 AM
    • Marked as answer by Haixia_XieModerator Friday, June 21, 2013 6:31 AM
    Friday, June 14, 2013 6:27 AM
  • Thanks a lot for looking into this, it did help us in confirming the behavior. Even we found out that the boundary format with 'equal to' sign is a valid format by going through some of the microsoft blogs. It might be something to do with the NIST validatory treating 'equal to' sign in a different manner. Will try to get in touch with someone from NIST team on this.

    sharath

    Wednesday, June 19, 2013 2:02 PM