header folding
Certainly -
Content-Type: multipart/report; report-type=disposition-notification;
boundary="----=_Part_451_509043770.1197585335803"
------=_Part_451_509043770.1197585335803
Content-type: text/plain
Content-Transfer-Encoding: 7bit
AS2 message received.
------=_Part_451_509043770.1197585335803
Content-type: message/disposition-notification
Content-Transfer-Encoding: 7bit
Reporting-UA: m-e-c as2
Original-Recipient: rfc822; DAZ
Final-Recipient: rfc822; DAZ
Original-Message-ID:
Disposition: automatic-action/MDN-sent-automatically; processed
Received-Content-MIC: zeInHgSt0PCXb1awHZul6J7yGOw=, sha1
------=_Part_451_509043770.1197585335803--
This is an MDN that we sent to our trading partner. The content-type header line is folded so that the content-type and report-type appear on the same line, and the bounary appears on the next line. Now, according to all of the RFC standards that we have explored, header folding like this is allowed. For whatever reason, the Extol AS2 server software may be experiencing trouble with the folded header. This MDN works fine with other trading partners (many of whom use Drummond certified software from Sterling and Inovis, which implies that this is not some "certification issue"). Any thoughts about what could be causing the Extol server to not recognize the MDN? Is there anyway to unfold that header? We are using build 19 of mec as2.
Thanks for your help,
daz
Here is a sample that we were sent. This is an MDN that is apparently working with the Extol AS2 server. Note how the boundary is included on the same line with the rest of the Content-Type header data.
--_=7707920964263624Sterling7707920964263624MOKO
Content-Type:multipart/report;Report-Type=disposition-notification;boundary="_=7043739501562648Sterling7043739501562648MOKO"
--_=7043739501562648Sterling7043739501562648MOKO
Your message was successfully received and processed.
--_=7043739501562648Sterling7043739501562648MOKO
Content-Type: message/disposition-notification
Original-Recipient: rfc822;***********
Final-Recipient: rfc822;***********
Original-Message-ID:<307a4a24fe1541169db99aeaf22debe2@307a4a25fe1541169db99aeaf22debe2>
Received-Content-MIC: Ahj6vucXdDt8Jvlg1Yehkl2i+oo=,sha1
Disposition:Automatic-action/mdn-sent-automatically;processed
--_=7043739501562648Sterling7043739501562648MOKO--
--_=7707920964263624Sterling7707920964263624MOKO
Content-Type: Application/pkcs7-signature;name=EDIINTSIG.p7s
We were able to fix this problem by adding in a "Content-Length" header to the buildHeaderForSyncMDN method of the AS2ServerRemoteImpl class. The actual content length value comes from message.getRawData().length . Please include a content-length header in the MDN in the next build of the as2 server (we would much rather be using m-e-c's 'official' version than our own current build).
Thanks!
-daz
© 1999-2008 mendelson-e-commerce GmbH. All right reserved.
Hello, everybody.
We're having an issue with our MDNs being recognized as such by Extol 5.x AS2 Server. The mec software shows no error (everything in the transaction window is green). The Extol software on the receiving side gives an error of "HTTP response is not an MDN". We were told that it's possibly due to MIME header folding, since Drummond has revised its InterOP testing specs. Is there a way to prevent the headers from folding, so that at least we can eliminate this as a cause?
The strange thing is that we can send an AS2 message with the same folded headers and receive the Extol MDN without problem. It's sending
in the other direction that raises the MDN issue. It's possible that header folding is not the cause, so we are open for any suggestion that anyone may have.
Thank you, and Happy Holidays.