I have the following use case: Sending a file from pyas2 to a partne

This is not as per AS2 standards, refer here <a href="https://tools.ietf.org/html/rfc4

Thanks for your reference. In Sectionn 4.2 <a href="https://tools.i

Parse MDN from response headers about django-pyas2 HOT 3 CLOSED

abhishek-ram commented on September 15, 2024

Parse MDN from response headers

from django-pyas2.

Comments (3)

abhishek-ram commented on September 15, 2024

This is not as per AS2 standards, refer here https://tools.ietf.org/html/rfc4130#section-7.4.2
If it had at least been in the body then something could have been done but since its not you need to ask your partner to either user a proper AS2 software or disable Request MDN for this partner and PyAs2 wont try to process this.

from django-pyas2.

adiroiban commented on September 15, 2024

Thanks for your reference.

In Sectionn 4.2 https://tools.ietf.org/html/rfc4130#section-4.2 i see this structure.

When no encryption or signature is used, the request is not wrapped in MIME... that is, no multipart.
Based on the same principle, I assumed that the MDN is also not wrapped.


4.2.  Structure of an Internet EDI MIME Message

   No encryption, no signature
      -RFC2616/2045
         -RFC1767/RFC3023 (application/EDIxxxx or /xml)

   MDN over HTTP, no signature
      -RFC2616/2045
        -RFC3798 (message/disposition-notification)

Also in section 7.4.2 I see

   When the message is
   unsigned, the transfer-layer ("outermost") entity-headers of the
   AS2-MDN contain the content-type header that specifies a content-type
   of "multipart/report" and parameters indicating the report-type, and
   the value of the outermost multipart boundary.

Here, with transfer-layer outermost, I understand the HTTP response/request headers or SMTP headers.

I now see that there is seprate librarty used by django-pyas2 to parse the MDN, I I guess that this should be closed anyway and moved there.

I have also tested JScape AS2 implementation which is advertised as "certified" and I see the same error.

from django-pyas2.

adiroiban commented on September 15, 2024

Thanks for your time. I got it wrong.

For the reference.
For unsigned MDN the sync response should look like.

HTTP/1.0 200 OK
AS2-From: 0123456780000
AS2-To: "\"  as2Name  \""
AS2-Version: 1.1
Message-ID: <709700825.1028122454671.JavaMail@ediXchange>
Content-Type: multipart/report; report-type=disposition-notification; boundary="----=_Part_336_6069110.1040310218718"

------=_Part_336_6069110.1040310218718
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

The message <x12.edi> sent to Recipient <AS2 Test> on Thu, 19 Dec
2002 15:04:18 GMT with Subject <async MDN request> has been received.
The EDI Interchange was successfully decrypted, and its integrity was
verified.  In addition, the sender of the message, Sender
<as2_company> at Location http://10.240.1.2:8201/exchange/as2_company
was authenticated as the originator of the message.  There is no
guarantee, however, that the EDI interchange was syntactically
correct, or that it was received by the EDI application/translator.

------=_Part_336_6069110.1040310218718
Content-Type: message/disposition-notification
Content-Transfer-Encoding: 7bit

Reporting-UA: AS2@test:8101
Original-Recipient: rfc822; "AS2 Test"
Final-Recipient: rfc822; "AS2 Test"
Original-Message-ID: <#as2_company#01#a4260as2_companyout#>
Disposition: automatic-action/MDN-sent-automatically; processed
Received-Content-MIC: Hes6my+vIxIYxmvsA+MNpEOTPAc=, sha1

------=_Part_336_6069110.1040310218718--

from django-pyas2.

Parse MDN from response headers about django-pyas2 HOT 3 CLOSED

Comments (3)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent