Base64 Content Transfer Encoding

[MakakWasTaken]

I have recently started receiving the error: Error Reading Input Stream.

I suspect that it might be caused by the partner switching from sending the attachment using the binary Content-Transfer-Encoding to base64.

Is it possible to receive documents using this encoding?

[phax]

Was the Content-Transfer-Encoding set on a specific MIME part, of was it set on the full message?

[MakakWasTaken]

The raw content of the transaction looks like the following (With soap envelope and attachment redacted):

--=-VahA61BNdImrmvkKe6eQ4A==
Content-Type: application/soap+xml; charset=utf-8

** SOAP ENVELOPE **
--=-VahA61BNdImrmvkKe6eQ4A==
Content-Type: application/octet-stream
Content-Id: <58d2a43d-3f24-4544-9f30-766f78988b12.edi>
Content-Disposition: attachment
Content-Transfer-Encoding: base64

**BASE64 STRING**

--=-VahA61BNdImrmvkKe6eQ4A==--

EDIT:

OBS. I am not sure if this specifically is causing the overall problem that I am having, so I'll provide some more information:
The below error started happening after our partner switched to a new system. The only difference I noticed in the multipart was that the Content-Transfer-Encoding had switched from binary to base64. So I concluded that this was the cause of the error.

The exception is:
com.helger.web.multipart.MultipartMalformedStreamException: Stream ended unexpectedly

I am not sure why this error suddenly started happening. It is the same files that they used to send before the update.

Full Stacktrace

Internal error processing AS4 request
Technical details:
javax.mail.MessagingException: Error reading input stream;
  nested exception is:
	com.helger.web.multipart.MultipartMalformedStreamException: Stream ended unexpectedly
1.: javax.mail.internet.MimeBodyPart.<init>(MimeBodyPart.java:172)
2.: com.helger.phase4.servlet.AS4IncomingHandler.parseAS4Message(AS4IncomingHandler.java:215)
3.: com.helger.phase4.servlet.AS4RequestHandler.handleRequest(AS4RequestHandler.java:1725)
4.: com.helger.phase4.servlet.AS4RequestHandler.handleRequest(AS4RequestHandler.java:1764)
5.: com.helger.phase4.servlet.AS4XServletHandler.handleRequest(AS4XServletHandler.java:309)
6.: com.helger.phase4.servlet.AS4XServletHandler.handleRequest(AS4XServletHandler.java:343)
7.: com.helger.xservlet.handler.simple.XServletHandlerToSimpleHandler.onRequest(XServletHandlerToSimpleHandler.java:245)
8.: com.helger.xservlet.AbstractXServlet._invokeHandler(AbstractXServlet.java:345)
9.: com.helger.xservlet.AbstractXServlet.service(AbstractXServlet.java:533)
10.: javax.servlet.http.HttpServlet.service(HttpServlet.java:764)
11.: com.helger.xservlet.AbstractXServlet.service(AbstractXServlet.java:587)
  [34 elements omitted -- org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:227)]
==> [1] caused by com.helger.web.multipart.MultipartMalformedStreamException: Stream ended unexpectedly
1.: com.helger.web.multipart.MultipartStream$MultipartItemInputStream._makeAvailable(MultipartStream.java:820)
2.: com.helger.web.multipart.MultipartStream$MultipartItemInputStream.read(MultipartStream.java:705)
3.: java.base/java.io.BufferedInputStream.fill(BufferedInputStream.java:252)
4.: java.base/java.io.BufferedInputStream.read1(BufferedInputStream.java:292)
5.: java.base/java.io.BufferedInputStream.read(BufferedInputStream.java:351)
6.: com.sun.mail.util.ASCIIUtility.getBytes(ASCIIUtility.java:278)
7.: javax.mail.internet.MimeBodyPart.<init>(MimeBodyPart.java:170)
  [44 elements omitted -- com.helger.phase4.servlet.AS4IncomingHandler.parseAS4Message(AS4IncomingHandler.java:215)]

[MakakWasTaken]

After some more research I have discovered that the partner also switched from sending with CRLF to LF line endings. According to this post this could also be the cause of the problem.

To this extent I have some questions:

1. Is it possible to receive base64 encoded attachments already?
2. Is it possible to set up receiving for both types of line endings?

[MakakWasTaken]

That makes sense, I wasn't aware that there was a standard for the line endings 😄. I'll forward the standard to them and ask if they're able to comply.

I think they have developed their own solution, but I am not 100% sure. I have a name of the system, but I am not sure i'm allowed to post it here. I can send it in an email if you'd like it.

[phax]

Yes, please send it to me via email. Feel free to also put me in CC when escalating issues - I am happy to help on the technical issues...

[MakakWasTaken]

I got my partner convinced to change their system using the above mentioned standard 😄.

In regards to the original question on whether there is support for base64 encoded messages, I'll have a look when it is implemented (Should be implemented during this week or at the latest next week).

I'll keep you in mind if any more technical problems arise 😉

Thanks again

[phax]

@MakakWasTaken were you able to resolve the issue?

[MakakWasTaken]

Yes, it seems to be working fine with the base64 encoding on the attachment.

The other issue has also been resolved.

[arj03]

Ran into the same kind of error, content must be CRLF encoded and not LF