Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Mon, 20 May 2013 10:13:15 +0000 (UTC)
From: "Sergey Beryozkin (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12648415.1369044439015.346093.1369044795947@arcas>
In-Reply-To: <JIRA.12648415.1369044439015@arcas>
References: <JIRA.12648415.1369044439015@arcas>
Subject: [jira] [Commented] (CXF-5024) Update HTTP Transport HTTPHeaders
 utility to correctly represent some complex headers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CXF-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661882#comment-13661882 ] 

Sergey Beryozkin commented on CXF-5024:
---------------------------------------

See also
http://svn.apache.org/r1481920

(Header update to support the Date conversion)
                
> Update HTTP Transport HTTPHeaders utility to correctly represent some complex headers
> -------------------------------------------------------------------------------------
>
>                 Key: CXF-5024
>                 URL: https://issues.apache.org/jira/browse/CXF-5024
>             Project: CXF
>          Issue Type: Task
>          Components: Transports
>            Reporter: Sergey Beryozkin
>            Assignee: Sergey Beryozkin
>            Priority: Minor
>             Fix For: 3.0.0
>
>
> Date and Locale toString() conversion does not correctly represent these objects as HTTP header values. 
> HTTP Link and Set-Cookie headers have to be added as separate HTTP headers (one value - new line). 
> This is typically an issue of the JAX-RS runtime, but the proper support for Date & Locale headers, as well as for Set-Cookie, may be of use for WS services too.
> This can not be implemented in the JAX-RS runtime as the TCK enforces that custom header values like Locale, Date, etc are not converted until the data are written to the stream

--
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