[
https://issues.apache.org/jira/browse/CXF-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500523#comment-13500523
]
Hagen Raab commented on CXF-4482:
---------------------------------
This fix introduces a new problem. The LF (w/o CR) leads to problems with .NET
SOAP clients (talking to CXF servers with with fix). .NET refuses the SOAP
message. I think it's because the lonely LF. (tested with MTOM, SOAP12 binding)
I also think that replacing a CRLF by LF in the header is not valid HTTP.
> AttachmentSerializer puts an extra new line
> -------------------------------------------
>
> Key: CXF-4482
> URL: https://issues.apache.org/jira/browse/CXF-4482
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.6.1
> Reporter: Kirill Kadyrko
> Assignee: Freeman Fang
> Fix For: 2.4.10, 2.5.6, 2.6.3, 2.7.0
>
>
> _AttachmentSerializer_ always puts an extra new line before writing the root
> attachment boundary and headers. Because of that the HTTP request which
> contains only attachments has two line breaks after request headers. That is
> not understood by some service providers and they do not process the request.
> For example:
> {code}
> ...
> Pragma: no-cache
> Connection: keep-alive
> Content-Length: 92010
> <new line>
> <another new line>
> --uuid:467a6f94-55c4-43fe-9e4a-09d63b0bc589
> Content-Type: application/xml
> ...
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
