[jira] [Resolved] (CXF-6379) Separate HTTP headers for multiple header values not possible - bug in CXF-3714 fix

["Sergey Beryozkin (JIRA)" <ji...@apache.org>]

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

Sergey Beryozkin resolved CXF-6379.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.5
                   2.7.16
                   3.1.0
         Assignee: Sergey Beryozkin

The typo has been fixed, thanks. HttpConduit can check Set-Cookie if it is configured to auto-maintain the session

> Separate HTTP headers for multiple header values not possible - bug in CXF-3714 fix
> -----------------------------------------------------------------------------------
>
>                 Key: CXF-6379
>                 URL: https://issues.apache.org/jira/browse/CXF-6379
>             Project: CXF
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 3.0.4
>            Reporter: Carsten Lohmann
>            Assignee: Sergey Beryozkin
>             Fix For: 3.1.0, 2.7.16, 3.0.5
>
>
> In CXF-3714 a property has been introduced to allow multiple HTTP header values to be added as separate headers.
> But the corresponding fix in 
> {{org.apache.cxf.transport.http.Headers#transferProtocolHeadersToURLConnection}} 
> doesn't look correct. See 
> https://fisheye6.atlassian.com/changelog/cxf?cs=6763178c36ae4392344f9e8e1ea3e714ba8a2520
> To me it looks like it should be 
> {code}
> connection.addRequestProperty(header, s)
> {code}
> in {{transferProtocolHeadersToURLConnection()}}, instead of
> {code}
> connection.addRequestProperty(HttpHeaderHelper.COOKIE, s)
> {code}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)