You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Thomas Papke (JIRA)" <ji...@apache.org> on 2018/10/01 06:55:00 UTC
[jira] [Resolved] (CXF-7857) Mtom/XOP response contain wrong
encoded Content-ID HTTP header (Rollback CXF-7317)
[ https://issues.apache.org/jira/browse/CXF-7857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Papke resolved CXF-7857.
-------------------------------
Resolution: Fixed
[~deki] has already reverted the issue under CXF-7317, this issue is just for tracking purpose - so setting it do resolve.
> Mtom/XOP response contain wrong encoded Content-ID HTTP header (Rollback CXF-7317)
> ----------------------------------------------------------------------------------
>
> Key: CXF-7857
> URL: https://issues.apache.org/jira/browse/CXF-7857
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.1.16, 3.2.5, 3.2.6
> Reporter: Thomas Papke
> Priority: Major
> Fix For: 3.1.17, 3.2.7
>
>
> The bugfix CXF-7317 introduce an issue with the encoding of the Content-ID HTTP header.
> Full discussion can be found here:
> https://lists.apache.org/thread.html/81f6547983622663da5319707c5510c244ee3ecb0a958c0e2aca1959@%3Cusers.cxf.apache.org%3E
> As discussed in the mailing list, CXF-7317 will be rolled-back. This issue is just for tracking purpose in the release notes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)