Hello all, I think some help regarding the content-ID in the HTTP header in context of XOP / mtom attachments.
As part of https://issues.apache.org/jira/browse/CXF-1900 somethings was fixed that the Content-ID is NOT url encoded. As part of https://issues.apache.org/jira/browse/CXF-2669 a small improvement was implemented, but the issue description still define that the Content-ID and the Message-ID in the HTTP headers are NOT url encoded The "bugfix" https://issues.apache.org/jira/browse/CXF-7317 in one of the last bugfix releases (3.2.5) seems to rollback the behavior of CXF-1900 (at least from my understanding). Now the question: What is correct and why? From my understanding the fix with CXF-7317 was wrong and violates rfc2392. But maybe someone else could clarify this why CXF-7317 is still ok. Thank you, Kind regards, Thomas InterComponentWare AG: Vorst?nde: Dr. Ralf Brandner, Hans Gerwing, Nils Effertz Aufsichtsratsvors.: Prof. Dr. Christof Hettich Unternehmenssitz: 69190 Walldorf, Altrottstra?e 31 AG Mannheim HRB 351761 / USt.-IdNr.: DE 198388516
