myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Freedman (JIRA)" <...@myfaces.apache.org>
Subject [jira] Resolved: (PORTLETBRIDGE-147) TCK bug: getRequestHeaderMapActionTest fails if content-length excluded by bridge but in request
Date Wed, 16 Jun 2010 17:22:23 GMT

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

Michael Freedman resolved PORTLETBRIDGE-147.
--------------------------------------------

    Fix Version/s: 1.0.0
                   2.0.0
       Resolution: Fixed

Updated TCK test to account for content-length in underlying request but the bridge says its
value is -1

> TCK bug:  getRequestHeaderMapActionTest fails if content-length excluded by bridge but
in request
> -------------------------------------------------------------------------------------------------
>
>                 Key: PORTLETBRIDGE-147
>                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-147
>             Project: MyFaces Portlet Bridge
>          Issue Type: Bug
>          Components: Impl
>    Affects Versions: 1.0.0
>            Reporter: Michael Freedman
>            Assignee: Michael Freedman
>             Fix For: 1.0.0, 2.0.0
>
>
> By spec the bridge is supposed to exclude the content-length header if getContentLength
returns -1.  The getRequestheaderMapActionTest fails if the request contains a content-length
header (say its a wsrp call and this header is about the soap message) when it compares that
all headers in the request are in the bridge headerMap.  The test should special case this
and check that if the header is content-length and its not in the headerMap then to just continue
on as this is corerct.

-- 
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