none
Invalid character in XML Doc RRS feed

  • Question

  • i'm using HTTP Adapter to send an xml file to a client.
    in my orchestration i made a massage assignment to add the headers that are requierd from my client:

    MessageEnd = MessageORA;
    
    MessageEnd(*)= MessageORA(*);
    
    MessageEnd(HTTP.UserHttpHeaders)= "sender-id: 074\r\nrquid: 86E94772-21AD-41B8-9084-0E0215EF46D3\r\ncontent-type: application/octet-stream";
    
    
    the problem is that when i send the message i get response from my client that i am missing those header:
    <ShortDesc>Invalid or missing HTTP Header sender-id or rquid</ShortDesc>
    any one can help please ???
    • Changed type Montherz Tuesday, December 29, 2009 12:55 PM Invalid character
    • Edited by Montherz Tuesday, December 29, 2009 12:56 PM
    Monday, December 28, 2009 1:54 PM

Answers

  • solved by adding
    application/octet-stream; charset=UTF-8

    in the HTTP send port content type property

    • Marked as answer by Montherz Sunday, January 3, 2010 11:50 AM
    Sunday, January 3, 2010 11:50 AM

All replies

  • Solved that issue ..

    It seems that my host instance needs to restart to applay the new changes .... but i have another problem :P


    when i send to my client i get an internal error message after analizing the issue it seems that the XML doc that i have sent have an invalid character on top of it and that creates this error.

    From where did that charater come?
    how do i handle that issue ?


    i hope that some one will help me in this :(


    Thank You 
    Tuesday, December 29, 2009 12:45 PM
  • Try using a tool like Fiddler to inspect the outbound HTTP stream to see if it is getting in there or if it is getting formatted incorrectly.

    Thanks,
    If this answers your question, please use the "Answer" button to say so | Ben Cline
    Tuesday, December 29, 2009 4:53 PM
    Moderator
  • it appears that biztalk is placing ? character on top of my message ??

    is that normal ?

    Wednesday, December 30, 2009 8:02 AM
  • any help please
    • Marked as answer by Montherz Sunday, January 3, 2010 11:47 AM
    • Unmarked as answer by Montherz Sunday, January 3, 2010 11:50 AM
    Sunday, January 3, 2010 10:20 AM
  • solved by adding
    application/octet-stream; charset=UTF-8

    in the HTTP send port content type property

    • Marked as answer by Montherz Sunday, January 3, 2010 11:50 AM
    Sunday, January 3, 2010 11:50 AM