-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Content type is quoted leading to boundary of multipart being double quoted #95
Comments
Yes I noticed that myself, and that's why 4.4.3 was released - that should fix the issue. |
I just tested it and it works fine again. Sorry for any inconvenience it caused. |
I am still experiencing it with 4.4.3:
Edit: I have used curl for the output above, mendelson gives me the following output
|
Well, that is a bit weird. Prior to 4.4.2 no header was quoted, so I'm confused why it is quoted now. |
I am not getting a dump for the outgoing message (I enabled both incoming and outgoing, incoming does work but the MDN is not dumped). start: AS2ReceiverHandler line 412
this leads to the quoting of the content type (and other headers). In version 4.4.1 the method forEachHeaderLine looks different: |
Release 4.4.4 is out and should fix that. Sorry for inconvenience. Please confirm that it works. Thx. |
I can confirm that strings are no longer quoted in 4.4.4 in my case. Tested with curl and checked output manually and mendelson also works again. Thank you for the quick fix and release. |
Thanks for crosschecking :D |
Since version 4.4.2 mendelson can no longer process an MDN response received. Looking at the response it seems that the boundary of the multipart is an issue.
The entire content type seems to be quoted the wrong way:
Content-Type: "multipart/report; report-type=disposition-notification; boundary=\"----=_Part_0_578487367.1568197726076\""
I have not enabled the quote header values setting.
I have not found an RFC that specifies the content type in quotes. I believe the issue is the AS2HttpHeaderSetter setting the header according to the whole value and not the contents of the value.
The text was updated successfully, but these errors were encountered: