cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "abdelgadiri (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-5201) jaxrs2: unable to intercept response to add new response headers
Date Thu, 15 Aug 2013 08:17:48 GMT

    [ https://issues.apache.org/jira/browse/CXF-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740798#comment-13740798
] 

abdelgadiri commented on CXF-5201:
----------------------------------

Hi Sergey,

setting the header via "context.getHeaders().putSingle("headerName", headerValue)" is NOT
working.

I am injecting the HttpServletResponse object via "@Context private HttpServletResponse response"
and I get ThreadLocalHttpServletResponse instance injected. So how do I obtain an HttpServletResponseWrapper
instance ?

I tried injecting  "@Context private HttpServletResponseWrapper response" but my war file
failed to deploy.  
                
> jaxrs2: unable to intercept response to add new response headers
> ----------------------------------------------------------------
>
>                 Key: CXF-5201
>                 URL: https://issues.apache.org/jira/browse/CXF-5201
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 2.7.5, 2.7.6
>         Environment: windows
>            Reporter: abdelgadiri
>
> In a WriterInterceptor, one expects to be able to modify response headers via:
> //here using putSingle() but could also use on of the addXXX variants
> context.getHeaders().putSingle("headerName", headerValue);
> However, above is not working in 2.7.5/2.7.6 (@see JIRA-4986)
> As a workaround, one should be able to inject the HttpServletResponse object via: @Context
HttpServletResponse response;
> then be able to add headers directly to the response object e.g.,
> response.setHeader("headerName", headerValue);
> however, above is also not working in (2.7.5/2.7.6). This is not always reproducable
as sometimes my client does see the new headers in the received response. On closer look it
seems the added headers get lost when it is a @GET request as opposed to e.g., a @POST. Basically,
my test case (a @GET) always fails with a missing header in the received response even though
I am pretty sure the server had added the header. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message