OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (EBXMLMSG-52) Content-Disposition header requirement

Sander Fieten created EBXMLMSG-52:

             Summary: Content-Disposition header requirement
                 Key: EBXMLMSG-52
                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-52
             Project: OASIS ebXML Messaging Services TC
          Issue Type: Bug
          Components: AS4 Profile
            Reporter: Sander Fieten

In section 5.1.9 support for use of the "Content-Disposition" MIME header and its "filename" parameter is required. 

A payload however does not necessarily have a file name. It is unclear how the header should be used in such case.

For exchanging such info it also is more logical to use the PartProperties element in the ebMS messaging header. 

The text also refers to "MIME specification (IETF) [RFC2045]". This RFC however does not mention this header. It is defined in RFC2183.
The MIME packaging used by AS4 (SwA) is defined in RFC2387 (MIME Multi-Part). Section 4 of that RFC discusses the use of the Content-Disposition header and recommends not to use this header unless handling of the filename parameter is explicitly specified. This is not the case in ebMS V3/AS4. 

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]