[CXF-7682] context.get(MessageContext.HTTP_REQUEST_HEADERS) always returns null for client

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.1.16, 3.2.5
• Component/s: JAX-WS Runtime
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Jimmy Praet
• Created: 20/Mar/18 10:12
• Updated: 25/Mar/19 12:28
• Resolved: 02/Jun/18 05:26

Description

I have a client-side LogicalHandler that adds some HTTP headers and am noticing it causes the existing SOAPAction HTTP header (already added automatically by the JAX-WS runtime) to be removed.

My handler code looks like this:

public boolean handleMessage(LogicalMessageContext context) {
  Boolean outbound = (Boolean) context.get(MessageContext.MESSAGE_OUTBOUND_PROPERTY);
  if (outbound) {
    Map<String, List<String>> headers =
        (Map<String, List<String>>) context.get(MessageContext.HTTP_REQUEST_HEADERS);
    if (headers == null) {
      headers = new HashMap<String, List<String>>();
      context.put(MessageContext.HTTP_REQUEST_HEADERS, headers);
    }
    for (Map.Entry<String, String> entry : Tracer.getEntries().entrySet()) {
      headers.put(entry.getKey(), Collections.singletonList(entry.getValue()));
    }
  }
  return true;
}

I had a quick look at the code and noticed the LogicalMessageContextImpl#get(Object) always returns null on the client side (isRequestor() = true).

So my handler will create a new header map and put it on the context, which is internally mapped to key "org.apache.cxf.message.Message.PROTOCOL_HEADERS" here.

Issue Links

• links to: GitHub Pull Request #394
• links to: GitHub Pull Request #403