mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] Updated: (ASYNCWEB-4) caller supplied content is ignored, and some request headers may be added twice
Date Thu, 14 Feb 2008 00:27:09 GMT

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

Sangjin Lee updated ASYNCWEB-4:

    Attachment: ASYNCWEB-4.patch

Moving over a bug fix from the G sandbox.  Whenever we fix any issue, we will move it over
to asyncweb for consideration.

This issue has to do with handling user-supplied message bodies...

> caller supplied content is ignored, and some request headers may be added twice
> -------------------------------------------------------------------------------
>                 Key: ASYNCWEB-4
>                 URL: https://issues.apache.org/jira/browse/ASYNCWEB-4
>             Project: Asyncweb
>          Issue Type: Bug
>            Reporter: Sangjin Lee
>            Assignee: Rick McGuire
>         Attachments: ASYNCWEB-4.patch, GERONIMO-3839-v2.patch, GERONIMO-3839.patch
> Some request headers get special treatment by HttpRequestEncoder.  HttpRequestEncoder
does not make any effort in checking to see if they are present in the headers already.  As
a result, they may be added twice if one is not careful.  For example,
> - Content-Type & Content-Length are added by HttpRequestEncoder for POST requests,
and should not be added by callers.
> - Host & User-Agent are always added by HttpRequestEncoder, and should not be added
by callers as ordinary headers.
> Although one could argue that callers should not add these headers by hand, I think HttpRequestEncoder
still should ensure that they are not added twice.

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

View raw message