[
https://issues.apache.org/jira/browse/CXF-6528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693337#comment-14693337
]
Sergey Beryozkin commented on CXF-6528:
---------------------------------------
Are you using a non-CXF HTTP transport possibly in Camel ?
The problem with converting to String in ResponseBuilder was that it was
causing TCK failures, because a number of tests were written such that response
filters were expected to see the original Date (as far as I recall now) set on
ResponseBuilder.
Perhaps the right place to fix it would be in Camel CXF...
> JAX-RS "lastModified" generates timestamp with non-standard format
> ------------------------------------------------------------------
>
> Key: CXF-6528
> URL: https://issues.apache.org/jira/browse/CXF-6528
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Affects Versions: 3.0.0-milestone2
> Environment: ServiceMix 5.4.0
> Reporter: metatech
>
> In CXF 3.x (since CXF-5007), the date format has changed in the
> "Last-Modified" HTTP header generated by JAX-RS.
> In class org.apache.cxf.jaxrs.impl.ResponseBuilderImpl, the method
> "lastModified()" does not call the "toHttpDate" anymore.
> The format is now the default format used when calling "toString" on the date
> object.
> This format is not one of the 3 allowed by the HTTP specification (RFC2616,
> section 3.3.1).
> For instance, an HTTPClient will reject this date format :
> ====================
> Wrong date format for date Wed Aug 12 08:18:54 CEST 2015
> org.apache.commons.httpclient.util.DateParseException: Unable to parse the
> date Wed Aug 12 08:18:54 CEST 2015
> at
> org.apache.commons.httpclient.util.DateUtil.parseDate(DateUtil.java:170)
> at
> org.apache.commons.httpclient.util.DateUtil.parseDate(DateUtil.java:94)
> ====================
> Can you please restore the date conversion ?
> Thanks in advance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
