cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] Commented: (CXF-3112) Further problem with cookies in Jax-RS (similar to closed issue 3035)
Date Thu, 18 Nov 2010 13:08:16 GMT


Sergey Beryozkin commented on CXF-3112:

By the way - atom push tests are passing for me - if you could check whenever you get a chance
what might be going wrong then let me know please. May be systests/jaxrs/.../resources/
are not filtering out some of the log events in your dev environment 

> Further problem with cookies in Jax-RS (similar to closed issue 3035)
> ---------------------------------------------------------------------
>                 Key: CXF-3112
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 2.3.0, 2.2.11
>            Reporter: David Hagar
>         Attachments: 3112_patch.diff
> Prior to version 2.2.11, multiple cookies were not handled properly by the method org.apache.cxf.jaxrs.client.AbstractClient#setResponseBuilder(HttpURLConnection,
Exchange) -- this was resolved for some cookies, but it still breaks for others. Specifically,
any cookie that contains an "Expires" field now gets split into two objects by the aforementioned
> For example, if the header is:
> Set-Cookie: com.wm.visitor=10789493347;; Expires=Thu, 01-Oct-2020
23:44:22 GMT; Path=/
> Then response.getMetadata().get("Set-Cookie"); will return an array of length 2, with
values = {" com.wm.visitor=10789493347;; Expires=Thu", "01-Oct-2020 23:44:22
GMT; Path=/"
> I'm pretty sure this is a conflict of the code looking for date related headers conflicting
with the code looking for cookie related headers. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message