You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Kirill Kadyrko (JIRA)" <ji...@apache.org> on 2012/08/22 08:26:37 UTC

[jira] [Updated] (CXF-4482) AttachmentSerializer puts an extra new line

     [ https://issues.apache.org/jira/browse/CXF-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kirill Kadyrko updated CXF-4482:
--------------------------------

    Description: 
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}

  was:
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
Host: streamwork.com
Connection: keep-alive
Content-Length: 92010
<new line>
<another new line>
--uuid:467a6f94-55c4-43fe-9e4a-09d63b0bc589
...
Content-Type: application/xml
{code}

    
> 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
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira