Github user mlibbey commented on the issue:
https://github.com/apache/trafficserver/pull/749
The RFC portion didn't mandate removing Last-Modified. ("Since the goal of
a 304 response is to minimize information transfer when the recipient already
has one or more cached representations, a sender SHOULD NOT generate
representation metadata other than the above listed fields unless said metadata
exists for the purpose of guiding cache updates (e.g., Last-Modified might be
useful if the response does not have an ETag field)." I've seen one case where
others were expecting it to be their regardless of the ETag (because another
large commercial CDN does it that way).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
