geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick McGuire (JIRA)" <>
Subject [jira] Commented: (GERONIMO-3888) AsyncHttpClient does not handle Set-Cookie directive with an empty value
Date Wed, 05 Mar 2008 14:57:40 GMT


Rick McGuire commented on GERONIMO-3888:

I'd say that this module is largely in wrap-up mode right now.  People are using it, and we'll
apply bug fixes to it when they're reported (particularly when accompanied by patches :-)).
 It is not being used internally by Geronimo, but does provide some nice capabilities for
implementing applications running on Geronimo.  I believe there are others who intend on using
it in a production environment too. 

For the longer term, work is progressing in the Mina project to merge this into the AsyncWeb
subproject.  Currently, a lot of the API is undergoing a "rethink", which means the APIs will
likely change significantly.  This is the version that will be getting the buik fo the attention
for a Mina 2.0 version.  

> AsyncHttpClient does not handle Set-Cookie directive with an empty value
> ------------------------------------------------------------------------
>                 Key: GERONIMO-3888
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: AsyncHttpClient
>            Reporter: Alex Antonov
>            Assignee: Rick McGuire
>         Attachments: empty_cookie_value.patch
> The current version does not handle properly a case where a Set-Cookie header has an
empty value for a name. i.e
> Set-Cookie=token=; path=/; expires=Thu, 01 Jan 1970 00:00:00 GMT
> According to the rfc-2109 for the Set-Cookie header, the value is an optional property
and could be blank.

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

View raw message