[
https://issues.apache.org/jira/browse/CXF-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500933#comment-13500933
]
Freeman Fang commented on CXF-4482:
-----------------------------------
Hi Aki,
Thanks for the link. And you're right, we should have CRLF.
Actually after discussed with Dan, I realized that
AttachmentSerializer.writeProlog() method is used to write the very first
boundary and headers which means the underlying HTTP transport already has
output the CRLF after the HTTP header.
So we needn't have any other one.
Freeman
> 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.11, 2.5.7, 2.6.4, 2.7.1
>
> Attachments: crlf.jpg
>
>
> _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
