[CAMEL-9091] CXF Transport should convert response Date headers to HTTP-friendly format

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Fix Version/s: 2.16.0
• Component/s: camel-cxf
• Patch Info: Patch Available
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Sergey Beryozkin
• Created: 19/Aug/15 16:01
• Updated: 02/Sep/15 15:52
• Resolved: 02/Sep/15 15:52

Description

CXF converts response Date headers into HTTP friendly format in its own transport code.

When CXF (jaxrs) endpoints are accessed in Camel routes via Camel Transport (example, from Camel Jetty or Camel Servlet) the Date headers are converted in Camel components using the regular toString converters.
Thus the clients do not receive the expected HTTP-friendly Date representations.

CxfHeaderHelper should convert such Dates by default. The option is to be introduced to avoid the toString() conversion inside Camel CXF and let other components to do it if really needed.

Note that the current CXF Transport code is wrongly typed to expect the CXF response headers be already converted to String.

The patch updates the conversion code to check Dates, disable the conversion to String all together if really needed, and adds more tests

Issue Links

• Is contained by: CAMEL-9105 Camel DefaultHttpBinding should convert response Date headers to HTTP-friendly format
• is related to: CXF-6528 JAX-RS "lastModified" generates timestamp with non-standard format