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

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

As an additional check, I created the following Servlet filter to introspect 
the response headers which confirmed to me that the response header set from 
the JAX-RS interceptor is not being returned to the client.

@WebFilter(filterName = "ResponseDebugFilter", urlPatterns = {"/*"})
public class ResponseDebugFilter implements Filter {
    @Override
    public void init(FilterConfig filterConfig) throws ServletException {
        //do nothing
    }

    @Override
    public void doFilter(ServletRequest servletRequest, ServletResponse 
servletResponse, FilterChain filterChain)
            throws IOException, ServletException {

        //carry on as normal
        filterChain.doFilter(servletRequest, servletResponse);

        //print response headers on way out
        if (servletResponse instanceof HttpServletResponse) {
            Collection<String> headerNames = ((HttpServletResponse) 
servletResponse).getHeaderNames();
            for (String hn : headerNames) {
                Collection<String> headers = ((HttpServletResponse) 
servletResponse).getHeaders(hn);
                System.out.println("^^^^^^^^^^^^^^^^^^^^^^^^^^^^ found response 
header (" + hn + "): " + headers);
            }
        }
    }

    @Override
    public void destroy() {
        //do nothing
    }
}
                
> 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

Reply via email to