geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick McGuire (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (GERONIMO-3857) response header parsing is done incorrectly
Date Fri, 15 Feb 2008 11:44:07 GMT

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

Rick McGuire resolved GERONIMO-3857.
------------------------------------

    Resolution: Fixed

Committed revision 628025.  Mina 1.1.5 version
Committed revision 628026.  Mina 2.0 version 

Thanks Sangjin!

> response header parsing is done incorrectly
> -------------------------------------------
>
>                 Key: GERONIMO-3857
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3857
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: AsyncHttpClient
>    Affects Versions: 1.x
>            Reporter: Sangjin Lee
>            Assignee: Rick McGuire
>         Attachments: GERONIMO-3857.patch
>
>
> When we decode response headers, HttpDecoder separates name from value using ": " (note
the *single*space after the colon).  This is incorrect.  The HTTP spec says
> - The field value MAY be preceded by any amount of LWS, though a single SP is preferred.
> The separator pattern should be simply ":".  Then any preceding or trailing LWSP characters
(SP or HT) should be removed from the value.  This is a rather critical issue.  I had headers
like 
> Server: Foo
> Content-Length:62
> Connection: close
> (notice lack of space after "Content-Length:")
> HttpResponseDecoder cannot properly parse the above headers, and throws a StringIndexOutOfBoundsException.

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


Mime
View raw message