cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CXF-5024) Update HTTP Transport HTTPHeaders utility to correctly represent some complex headers
Date Tue, 26 Nov 2013 17:38:46 GMT

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

Daniel Kulp updated CXF-5024:
-----------------------------

    Fix Version/s:     (was: 3.0.0-milestone1)
                   3.0.0-milestone2

> 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-milestone2
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message