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:24:38 UTC
[jira] [Created] (CXF-4482) AttachmentSerializer puts an extra new
line
Kirill Kadyrko created CXF-4482:
-----------------------------------
Summary: 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
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}
--
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
[jira] [Assigned] (CXF-4482) AttachmentSerializer puts an extra new
line
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang reassigned CXF-4482:
---------------------------------
Assignee: Freeman Fang
> 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
>
> _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
[jira] [Commented] (CXF-4482) AttachmentSerializer puts an extra
new line
Posted by "Hagen Raab (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CXF-4482) AttachmentSerializer puts an extra
new line
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CXF-4482) AttachmentSerializer puts an extra
new line
Posted by "Kirill Kadyrko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500899#comment-13500899 ]
Kirill Kadyrko commented on CXF-4482:
-------------------------------------
Hi,
I think we should definitely use CRLFCRLF to separate HTTP headers and a body. What took place before the fix, was actually THREE line breaks after HTTP headers (CRLFCRLFCRLF). Maybe the most reasonable fix is to just remove the last CRLF? I've attached a screenshot.
> 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
[jira] [Updated] (CXF-4482) AttachmentSerializer puts an extra new
line
Posted by "Kirill Kadyrko (JIRA)" <ji...@apache.org>.
[ 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
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
[jira] [Updated] (CXF-4482) AttachmentSerializer puts an extra new
line
Posted by "Kirill Kadyrko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kirill Kadyrko updated CXF-4482:
--------------------------------
Attachment: crlf.jpg
> 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
[jira] [Commented] (CXF-4482) AttachmentSerializer puts an extra
new line
Posted by "Aki Yoshida (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500928#comment-13500928 ]
Aki Yoshida commented on CXF-4482:
----------------------------------
Hi Freeman,
could the problem be in the code that is reading the data back?
In the wire-format, we should be using CRLF for each line-break independently of the platform.
http://www.rfc-editor.org/rfc/rfc1521.txt
So, I think the writing part is correct.
regards, aki
> 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
[jira] [Resolved] (CXF-4482) AttachmentSerializer puts an extra new
line
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang resolved CXF-4482.
-------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.4.10)
(was: 2.5.6)
(was: 2.6.3)
(was: 2.7.0)
2.7.1
2.6.4
2.5.7
2.4.11
> 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
>
>
> _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
[jira] [Resolved] (CXF-4482) AttachmentSerializer puts an extra new
line
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang resolved CXF-4482.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.7.0
2.6.3
2.5.6
2.4.10
commit fix
http://svn.apache.org/viewvc?rev=1375972&view=rev for trunk
http://svn.apache.org/viewvc?rev=1375978&view=rev for 2.6.x branch
http://svn.apache.org/viewvc?rev=1376357&view=rev for 2.5.x branch
http://svn.apache.org/viewvc?rev=1376358&view=rev for 2.4.x branch
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-4482) AttachmentSerializer puts an extra new
line
Posted by "Kirill Kadyrko (JIRA)" <ji...@apache.org>.
[ 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
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
[jira] [Updated] (CXF-4482) AttachmentSerializer puts an extra new
line
Posted by "Kirill Kadyrko (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CXF-4482) AttachmentSerializer puts an extra
new line
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500927#comment-13500927 ]
Freeman Fang commented on CXF-4482:
-----------------------------------
Hi,
Yeah, what we've done is remove the latest two CRLF.
You can try the latest snapshot tomorrow.
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
[jira] [Commented] (CXF-4482) AttachmentSerializer puts an extra
new line
Posted by "aki yoshida (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501075#comment-13501075 ]
aki yoshida commented on CXF-4482:
----------------------------------
Hi Freeman,
good to hear the root cause has been identified and fixed.
:-)
regards, aki
> 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