This repository has been archived by the owner on Oct 4, 2019. It is now read-only.
"Unable to get multipart/signed data content; Caused by: Missing start boundary" Sync MDN #22
Assignees
Labels
Comments
|
Can you please paste the stored message, headers and MDN here. Thanks |
|
message header: payload: mdn: I do noticed that I have multiple parts of the message in the inbox and mdn folders |
|
adding config.xml just in case |
|
Okay, I have no clue. I'm pretty sure, that the system transmits the messages correctly and the problem is at the receiving side. |
phax
added a commit
to phax/as2-lib
that referenced
this issue
May 29, 2018
|
Yes I could do that easily. Testing with incoming message from the Axway activator is tricky as we need to relay that to our partner. Could this be a misconfiguration where it is async instead of synchronous setup? Why is openas2 trying to upload a multipart file for something simple? |
|
The phrase |
|
This could possibly be the reason. Is this any different from the full
stack openAS2 application? I tested with the full OpenAS2 application and
it worked like a charm
…On Wed, May 30, 2018 at 2:24 PM, Philip Helger ***@***.***> wrote:
The phrase Caused by: Missing start boundary indicates, that they have
problem parsing the S/MIME message at all. An idea is, that they don't like
the lower cases HTTP header names (content-type vs. Content-Type), so
that they cannot find the start boundary indicator as in
content-type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-1;
boundary="----=_Part_2_673195815.1527585114273"
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#22 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAd3G5p6_OgWmZlBt-FForzCce8MPZb5ks5t3o96gaJpZM4URQXf>
.
--
Regards,
Choon Ming
PGP Key : 0xD7DE3175
Twitter : @choonming
Skype : gchoonming
|
|
Well, according to the HTTP specification, HTTP headers should be treated case-insensitive - maybe you can send a mail to Axway support and ask if that is a known issue??? |
|
Not sure if I can get any quick response from Axway as I am not a customer. Would it be possible to create a separate branch with the proper case for the headers? I checked with the source code for the full stack and all headers are like "Content-Type" etc. It'll be quicker to test it this way. |
|
additional information when i test using the full openas2 stack msgheader: mdn header: payload: |
|
Sorry, public holiday yesterday. So it seem to work... I will try to create a version with case sensitive headers asap. Will keep you posted. |
|
Okay, I thought this through and checked the code:
|
I ran this The /tmp folder is empty even after i've sent some test data to another local openas2 instance This is the log output |
|
I seem to have a similar problem and have traced it down to the Content-Type lines (note the newline after "sha-1;", this is a folded header): I am currently looking for a way to deactivate the folding feature, would appreciate pointers on where to look. |
|
It seems header unfolding is only applied to incoming http request headers and not on headers in responses. As a workaround, I replaced the following lines in with which is not brilliant, but it fixes the problem for now. Is there a better way to achieve this? |
|
I see the issue. public void forEachHeaderLine (@Nonnull final Consumer <? super String> aConsumer)
{
for (final Map.Entry <String, ICommonsList <String>> aEntry : m_aHeaders.entrySet ())
{
final String sKey = aEntry.getKey ();
for (final String sValue : aEntry.getValue ())
aConsumer.accept (sKey + ": " + sValue);
}
}it should be public void forEachHeaderLine (@Nonnull final Consumer <? super String> aConsumer)
{
for (final Map.Entry <String, ICommonsList <String>> aEntry : m_aHeaders.entrySet ())
{
final String sKey = aEntry.getKey ();
for (final String sValue : aEntry.getValue ())
aConsumer.accept (sKey + ": " + getUnifiedValue (sValue));
}
} |
phax
added a commit
to phax/ph-commons
that referenced
this issue
Feb 28, 2019
|
Release 4.2.2 will solve the multiline problem |
|
Integrated and verified. Sincerely appreciate the effort. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm using the master branch for the as2-server deployment with sync MDN with a partner which uses axway activator. They are sending a message to us to be processed. We are getting a failed status from their end with the following message:
I received the message successfully and able to de-crypt the payload.
The text was updated successfully, but these errors were encountered: